Nesting SA within SA

.NET obfuscator and automated error reporting

Nesting SA within SA

Postby RobPerkins » Tue Feb 11, 2014 7:22 pm

I have a DLL which was built and then obfuscated and encrypted and dependency-merged with SA 6, which is working very well.

What will happen if I try to take that transformed DLL and merge it (just merge it, no further obfuscation on that code) as a dependency in an EXE assembly with SA?
Posts: 2
Joined: Tue Feb 11, 2014 7:19 pm

Postby jessica.ramos » Thu Feb 13, 2014 12:08 am

Hi Rob!

When you try to merge it, SmartAssembly will warn (when you hover over) that the assembly being merged has already been processed by SA and may lead to unexpected results. It will still let you go ahead with building though.

I think that so long as you don't apply any other options onto the assembly after merging it, and if the application isn't too complicated, there is a good chance that it would work out fine. Of course, what works and doesn't work is subjective to each application--the best way of knowing what will happen is to test it and see : )

Sorry to not have a more definitive answer!
Jessica Ramos
Technical Support
Red Gate Software Ltd.
Posts: 544
Joined: Mon Apr 23, 2012 12:13 pm

Postby RobPerkins » Thu Feb 27, 2014 6:11 pm


What about just embedding it as a dependency, rather than a merge?
Posts: 2
Joined: Tue Feb 11, 2014 7:19 pm

Return to SmartAssembly 6

Who is online

Users browsing this forum: No registered users and 1 guest