Comments
Sort by recent activity
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.
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?
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 ...
Sorry you've having these problems; how big are the input assemblies, how many are you merging together, and what options have you got turned on? These can drastically affect how much memory SA uses. / comments
Sorry you've having these problems; how big are the input assemblies, how many are you merging together, and what options have you got turned on? These can drastically affect how much memory SA uses.
When you merge in an assembly, the identity of that type changes. This message is because something is looking for that type in the old assembly, when it's been moved into the new assembly.
Unfortunately, there are many things that can be doing this. Maybe you've hard-coded the assembly name as a string somewhere in the code, or you're using reflection in some fashion? I can't be more specific than that I'm afraid, as it very much depends on what your code, and assemblies that are being referenced, actually does. Try doing a string search for the old assembly name in your codebase. / comments
When you merge in an assembly, the identity of that type changes. This message is because something is looking for that type in the old assembly, when it's been moved into the new assembly.
Unfortu...
Unfortunately, an embedded assembly isn't actually processed by SmartAssembly. You're getting that message because the exception reporting infrastructure required to route the exception to the right place hasn't been added to the assembly you're embedding. This infrastructure is only added when assemblies are merged, not when they're embedded.
You'll need to merge the assembly, instead of embed it. / comments
Unfortunately, an embedded assembly isn't actually processed by SmartAssembly. You're getting that message because the exception reporting infrastructure required to route the exception to the righ...
Added in SmartAssembly 6.6 Pro, Method Parent Obfuscation is a new obfuscation method that no current decompiler can undo.
However, no obfuscation method is completely secure; once your application is on a user's computer, there is nothing to stop them from trying to either reverse it or crack it; I recently wrote a blog post covering exactly this issue. / comments
Added in SmartAssembly 6.6 Pro, Method Parent Obfuscation is a new obfuscation method that no current decompiler can undo.
However, no obfuscation method is completely secure; once your application...