Pruning Non Managed Code

.NET obfuscator and automated error reporting

Pruning Non Managed Code

Postby lbargers » Mon Dec 06, 2010 3:50 pm


Im beginning obfuscation on a project, and I get the error the assembly "StandardImport, Version=XXXXX, Culture=neutral, PublicKeyToken=null' contains non-managed code, which is not supported by SmartAssembly.

Do I use the pruning feature to cut out the non-managed code I do not wish to obfuscate?
Posts: 3
Joined: Mon Dec 06, 2010 3:41 pm

Postby Brian Donahue » Tue Dec 07, 2010 5:40 pm

Hello Larry,

SmartAssembly only supports obfuscation on 100% managed-code assemblies. Mixed assemblies can't be processed by SmartAssembly, no workarounds.

Brian Donahue
Posts: 6590
Joined: Mon Aug 23, 2004 9:48 am

Return to SmartAssembly 5

Who is online

Users browsing this forum: No registered users and 0 guests