Comments
Sort by recent activity
MarkAsReleased has been removed in 6.5; now, all map files are maintained indefinitely, making MarkAsReleased obsolete. / comments
MarkAsReleased has been removed in 6.5; now, all map files are maintained indefinitely, making MarkAsReleased obsolete.
In 6.5 we made the project configuration slightly less tolerant of options that simply don't make sense (in this case, specifying memory management on a dll). If the option isn't available in the UI for you to turn off, you'll need to edit the saproj file directly and change
<OtherOptimizations ManageMemory="1" />
to
<OtherOptimizations ManageMemory="0" />
that should get it working in 6.5. / comments
In 6.5 we made the project configuration slightly less tolerant of options that simply don't make sense (in this case, specifying memory management on a dll). If the option isn't available in the U...
Again, similar to IL disassembly, some sort of (not necessarily valid) C# can always be produced from a method. SmartAssembly isn't aimed at making it impossible to disassemble methods completely, it's protections are aimed at hiding the meaning of the code, which is ultimately what you use an obfuscator for.
Control flow obfuscation, name obfuscation, strings encoding and member refs proxy all hide the original meaning of the code; even if some C# can be constructed from the disassembled IL, working out what that code actually does it very hard. / comments
Again, similar to IL disassembly, some sort of (not necessarily valid) C# can always be produced from a method. SmartAssembly isn't aimed at making it impossible to disassemble methods completely, ...
There's a difference between successfully decompiling an assembly, and being able to understand it once it is decompiled. SmartAssembly obfuscates the IL within the method, but it is still IL that can be decompiled, as it has to do the same thing as the original assembly.
If you look closely at the disassembled code, the type & method names are missing and it can no longer generate correct C# or VB. Furthermore, features like strings encoding and member refs proxy, combined with control flow obfuscation and name obfuscation, further hide what the code is actually doing. / comments
There's a difference between successfully decompiling an assembly, and being able to understand it once it is decompiled. SmartAssembly obfuscates the IL within the method, but it is still IL that ...
If you've got SmartAssembly Pro, you can reference SmartAssembly.ReportException.dll and call ExceptionReporting.ReportException(Exception) manually, as described in Method 1 of this article: http://www.red-gate.com/supportcenter/C ... %2ftoc.htm
SimonC / comments
If you've got SmartAssembly Pro, you can reference SmartAssembly.ReportException.dll and call ExceptionReporting.ReportException(Exception) manually, as described in Method 1 of this article: http:...
Hi Jasmin; glad you like the product!
With regards to the issue with CFO, would it be possible to send the assemblies & saproj you're using to me (email link at the bottom of this post) so we can have a look and find out what's going wrong?
Thanks for trying it out
SimonC / comments
Hi Jasmin; glad you like the product!
With regards to the issue with CFO, would it be possible to send the assemblies & saproj you're using to me (email link at the bottom of this post) so we can h...
Looks like you're using some sort of late-binding mechanism. Obfuscation will break reflection-like scenarios, as obfuscation changes the name of everything.
You'll need to add obfuscation and/or pruning exclusions in the SmartAssembly UI for the members you're late-binding to, or (if you've got Pro edition) add various DoNotObfuscate attributes to your codebase (see http://www.red-gate.com/supportcenter/C ... 032253.htm) / comments
Looks like you're using some sort of late-binding mechanism. Obfuscation will break reflection-like scenarios, as obfuscation changes the name of everything.
You'll need to add obfuscation and/or p...
You'll be pleased to know that the next version of SmartAssembly, to be released very soon, will have support for WinPhone 7.1 and Silverlight 5, and we've also fixed the MandatoryPath not working for assemblies signed with the microsoft framework key. / comments
You'll be pleased to know that the next version of SmartAssembly, to be released very soon, will have support for WinPhone 7.1 and Silverlight 5, and we've also fixed the MandatoryPath not working ...
Both these issues are fixed in the SA 6.5 release candidate - http://www.red-gate.com/MessageBoard/vi ... hp?t=14201 / comments
Both these issues are fixed in the SA 6.5 release candidate - http://www.red-gate.com/MessageBoard/vi ... hp?t=14201
May I ask why the customer requires ILMerge support?
There are several things that would break if we fixed ILMerge by putting the attribute in different assemblies; most notably, tamper protection, level 3 name obfuscation, ref dynamic proxies, and strings encoding.
ILMerging processed assemblies is not a scenario we have designed the tool to support, and it would be useful to know why exactly this is required so we can look at other solutions to the problem. / comments
May I ask why the customer requires ILMerge support?
There are several things that would break if we fixed ILMerge by putting the attribute in different assemblies; most notably, tamper protection,...