Comments
Sort by recent activity
Thanks, but things compile just fine in the GUI. And they compile just fine from the command line.
Now, true, the next-level dependencies will be required to RUN the code, but shouldn't be necessary to COMPILE the code.
It's S/A that's demanding ALL dependencies required to RUN be in the build folder, not just those that are required to COMPILE. / comments
Thanks, but things compile just fine in the GUI. And they compile just fine from the command line.
Now, true, the next-level dependencies will be required to RUN the code, but shouldn't be necessa...
Oh, come on!
Can S/A at least list out all the dependencies it claims it needs at one time?
ERROR: Cannot find dependency 'Microsoft.Practices.EnterpriseLibrary.Common, Version=5.0.505.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35', which is required for assembly:
S/A is only telling me one supposedly required dependency at a time.
I'm trying to do this through TeamCity. It takes awhile for me to find out what the next "missing dependency" is. / comments
Oh, come on!
Can S/A at least list out all the dependencies it claims it needs at one time?
ERROR: Cannot find dependency 'Microsoft.Practices.EnterpriseLibrary.Common, Version=5.0.505.0, Culture=n...
There needs to be an option to manually add additional dependencies to the S/A project. / comments
There needs to be an option to manually add additional dependencies to the S/A project.
There needs to be an option to manually add additional dependencies to the S/A project. / comments
There needs to be an option to manually add additional dependencies to the S/A project.
I tried both, like the following:
[DoNotPruneType]
public static class X
{
[DoNotPrune]
public static IY Y { get { return new Y(); }
}
This didn't help.
Only by excluding it through the configuration, would it go.
To be honest, I've given up applying "pruning" to anything in the project. The risk of instability it creates by taking something out that really is used has turned into a much bigger risk of just leaving any unused code in the project. / comments
I tried both, like the following:
[DoNotPruneType]
public static class X
{
[DoNotPrune]
public static IY Y { get { return new Y(); }
}
This didn't help.
Only by excluding it through the configurati...
I figured out what went wrong. Or at least what I needed to fix it.
I followed the instructions on this page about attributes: http://www.red-gate.com/supportcenter/c ... Attributes
I started w/ the first option listed on the page, and added a reference to SmartAssembly.Attributes.dll, and then later used the 2nd option.
Even though the app no longer actually needed the reference to the S/A dll, it was still being referenced. And when deployed, insisted it couldn't run w/out the S/A being in the GAC.
I removed the reference, built, and deployed, and the problem went away.
Still weird that option #1 would cause this though.
Seems #2 would've been listed first. / comments
I figured out what went wrong. Or at least what I needed to fix it.
I followed the instructions on this page about attributes:http://www.red-gate.com/supportcenter/c ... Attributes
I started w/ th...
Unfortunately, your link indicates it requires a Mono dll library attached to work.
I found I could do it by the following:
Using the Assembly object from the .exe, get referenced assemblies via:
assembly.GetReferencedAssemblies()
Then w/in one of my library .dll's that I know will be merged via S/A, I get it's assembly name:
Assembly.GetExecutingAssembly().GetName().FullName
I have noticed that this name will show up in the reference list when the app has NOT been obfuscated. But this name will disappear AFTER obfuscation (because it's no longer an external library, it's been merged w/ the .exe).
I use this fact to differentiate between the two states. / comments
Unfortunately, your link indicates it requires a Mono dll library attached to work.
I found I could do it by the following:
Using the Assembly object from the .exe, get referenced assemblies via:
a...
I've since discovered that this only seems to be happening when errors are occuring w/in one set of class libraries. (In my case, classes close to Prism libraries).
Other code tends to pop up the error dialog generally in 5 seconds. / comments
I've since discovered that this only seems to be happening when errors are occuring w/in one set of class libraries. (In my case, classes close to Prism libraries).
Other code tends to pop up the ...
I've been painfully determining what can and what cannot be pruned in our WPF type application. I had narrowed down a set of problems to a namespace full of interfaces, but that namespace also included the equivalent of implementation classes.
In the end, it turns out a few implementation classes had some methods that weren't part of their parent interfaces that were being cut out.
Anyway, got me wondering if I ever have to worry about [DoNotPruneType] on an interface.
So far, anything remotely behaving like a View Model in the MVVM pattern cannot be pruned. S/A doesn't check for property usage w/in XAML. And since WPF binds everything as "object", I doubt it could anyway. / comments
I've been painfully determining what can and what cannot be pruned in our WPF type application. I had narrowed down a set of problems to a namespace full of interfaces, but that namespace also inc...
It turns out that checkbox is important for S/A to work properly. I remember now I had turned that option off because I have a 3rd party .dll that wasn't signed, so I couldn't check it.
Fortunately, great article here shows how to fix that problem:
Signing an Unsigned Assembly http://buffered.io/posts/net-fu-signing ... y-signing/
Now, w/ all .dlls signed, I could check the box, sign the assembly, and run S/A, and run the program. / comments
It turns out that checkbox is important for S/A to work properly. I remember now I had turned that option off because I have a 3rd party .dll that wasn't signed, so I couldn't check it.
Fortunatel...