Comments
Sort by recent activity
If your assembly targets .NET 3.5, then it should run successfully on windows 7 with .NET 3.5 and 4.5 installed (.NET 3.5 is installed by default on windows 7). SA will maintain the target framework version of the main assembly. / comments
If your assembly targets .NET 3.5, then it should run successfully on windows 7 with .NET 3.5 and 4.5 installed (.NET 3.5 is installed by default on windows 7). SA will maintain the target framewor...
Yes, this is an issue in SA. We probably couldn't support such assemblies as the main assembly, as we need to know what version of mscorlib to read, but we could support them as dependencies by simply defaulting to the mscorlib of the main assembly.
I've added this into the system as SA-1672 / comments
Yes, this is an issue in SA. We probably couldn't support such assemblies as the main assembly, as we need to know what version of mscorlib to read, but we could support them as dependencies by sim...
By default, SA will obfuscate all internal and private members of dlls, and public, internal and private members of exes.
If there's some internal or private members that aren't being obfuscated when they should be, you can turn on trace logging (http://www.red-gate.com/supportcenter/c ... a_Log_File) which logs everything that wasn't obfuscated with a reason why it wasn't. / comments
By default, SA will obfuscate all internal and private members of dlls, and public, internal and private members of exes.
If there's some internal or private members that aren't being obfuscated wh...
If the assembly is a dll, no public members are pruned at all. If the assembly is an exe, all public members are pruned if they are not used elsewhere. This includes public interfaces.
May I ask what prompted this question? / comments
If the assembly is a dll, no public members are pruned at all. If the assembly is an exe, all public members are pruned if they are not used elsewhere. This includes public interfaces.
May I ask wh...
Hi Koen,
For information, what would you expect SmartAssembly to be able to do with .winmd files? What scenarios would be useful in your situation, and your WinRT apps?
thanks,
SimonC / comments
Hi Koen,
For information, what would you expect SmartAssembly to be able to do with .winmd files? What scenarios would be useful in your situation, and your WinRT apps?
thanks,
SimonC
Are you merging the .NET 4 dependencies into the main assembly? / comments
Are you merging the .NET 4 dependencies into the main assembly?
Make sure you are running SmartAssembly.com from the commandline rather than SmartAssembly.exe. The com file provides a standard CLI interface, rather than opening the GUI. / comments
Make sure you are running SmartAssembly.com from the commandline rather than SmartAssembly.exe. The com file provides a standard CLI interface, rather than opening the GUI.
Which version of SmartAssembly are you using? An identical issue was reported on 6.5, and was fixed in 6.6 (the latest release version is 6.7) / comments
Which version of SmartAssembly are you using? An identical issue was reported on 6.5, and was fixed in 6.6 (the latest release version is 6.7)
If you contact our support group at https://www.red-gate.com/supportcenter/ContactSupport, they'll be able to give you help and possibly a workaround for your specific situation. / comments
If you contact our support group at https://www.red-gate.com/supportcenter/ContactSupport, they'll be able to give you help and possibly a workaround for your specific situation.
That's a very, very big solution! The reason embedding works but merging throws an OOM exception is that SA has to do very little to embed an assembly; simply take the assembly bytes, compress and encrypt them, and put them into the final assembly resources.
However, to merge an assembly, it needs to build up several layers of datastructures representing the input and output assemblies, and then transform those in a consistent way according to the options selected. This takes far more memory than simply embedding a raw assembly. There's no hardcoded limitation, it's only limited by the amount of available RAM in your computer and various limitations imposed by the CLR itself.
With regards to your exception problems, there is likely a workaround for your specific situation. I recommend you contact support to open a proper support ticket; they'll be able to help you more specifically. You can contact them using the support page at https://www.red-gate.com/supportcenter/ContactSupport / comments
That's a very, very big solution! The reason embedding works but merging throws an OOM exception is that SA has to do very little to embed an assembly; simply take the assembly bytes, compress and ...