Comments
Sort by recent activity
When you merge and embed dependencies they all end up in the main assembly.
If you want to separately process the DLLs with SmartAssembly , then you need to create a separate SmartAssembly project.
SmartAssembly does not obfuscate public members of DLLs, so that they can still be called from elsewhere. / comments
When you merge and embed dependencies they all end up in the main assembly.
If you want to separately process the DLLs with SmartAssembly , then you need to create a separate SmartAssembly project....
Hi,
The removal of custom attributes is not intended behaviour. Does it occur when there are no SA features enabled ? / comments
Hi,
The removal of custom attributes is not intended behaviour. Does it occur when there are no SA features enabled ?
Hi,
Sorry you're having problems with v6.5.
In many cases v6.5 is faster. What features are you using ? Are you merging or embedding large dependencies ?
Can you isolate which SA feature is causing the error in the processed assembly?
(There is a recently fixed bug relating to custom attributes processing which occurs with no features enabled. If that is the case for you , then I can supply a patched version) / comments
Hi,
Sorry you're having problems with v6.5.
In many cases v6.5 is faster. What features are you using ? Are you merging or embedding large dependencies ?
Can you isolate which SA feature is causi...
Hi,
Firstly I should say that v6.5 is a re-architecture which is why it's performance is very different to v6.2 (in many cases better, but some cases worse).
SmartAssembly 6.6 is a recently released update and contains bug fixes and some memory improvements. v6.6 is a recommended update for all users of SmartAssembly 6.5. http://www.red-gate.com/supportcenter/C ... rtAssembly
Please give it a try and let me know if there are still performance problems. / comments
Hi,
Firstly I should say that v6.5 is a re-architecture which is why it's performance is very different to v6.2 (in many cases better, but some cases worse).
SmartAssembly 6.6 is a recently releas...
I think this has been answered here: http://www.red-gate.com/MessageBoard/vi ... hp?t=14073 / comments
I think this has been answered here:http://www.red-gate.com/MessageBoard/vi ... hp?t=14073
We believe we have fixed this bug in the latest version of SmartAssembly.
Please click on “Check For Updates†(under “Tools†on the left hand side) and upgrade SmartAssembly. (to v6.5.2.21)
Please let us know if the problem is fixed (or not) / comments
We believe we have fixed this bug in the latest version of SmartAssembly.
Please click on “Check For Updates†(under “Tools†on the left hand side) and upgrade SmartAssembly. (to v6.5.2.21)
P...
I am not sure why you don't have access to the code until after it has been processed by Smartassembly ? Do you have a Smartassembly license ?
The supported way to use Smartassembly is to apply it last , and not to use reflection on obfuscated code. / comments
I am not sure why you don't have access to the code until after it has been processed by Smartassembly ? Do you have a Smartassembly license ?
The supported way to use Smartassembly is to apply i...
OK. Using reflection on obfuscated code often causes issues.
Could you add the licensing wrapper to your code and then process with SA? (SA generally works best when it is done last) / comments
OK. Using reflection on obfuscated code often causes issues.
Could you add the licensing wrapper to your code and then process with SA? (SA generally works best when it is done last)
Execute Assembly probably finds the entry point using
public virtual MethodInfo EntryPoint { get; }
(http://msdn.microsoft.com/en-us/library ... point.aspx)
Your best option is to use that rather than trying to manually lookup the entry point in the obfuscated assembly. / comments
Execute Assembly probably finds the entry point using
public virtual MethodInfo EntryPoint { get; }
(http://msdn.microsoft.com/en-us/library ... point.aspx)
Your best option is to use that rather t...
You can exclude code from obfuscation to avoid problems.
This can be done via the SmartAssembly GUI or in code using custom attribute (http://www.red-gate.com/supportcenter/C ... rtAssembly) / comments
You can exclude code from obfuscation to avoid problems.
This can be done via the SmartAssembly GUI or in code using custom attribute (http://www.red-gate.com/supportcenter/C ... rtAssembly)