Home - Forums-.NET - Spices.Net - MSBuild Integration

Spices.Net

NET code security, tools to protect, obfuscate, tamper defense, code and data safety, recover, convert, optimize, explore, browse and analyze .Net software.

This forum related to following products: Spices.Net Suite, Spices.Net Obfuscator, Spices.Net Decompiler

MSBuild Integration
Link Posted: 19-Apr-2012 11:52
Hi,

I've successfully obfuscated my application using the Spices.NET UI.

I'm now trying to reproduce this on my Team Foundation Server. I've managed to invoke MSBuild as explained in the documentation to do the obfuscation.

I have a few questions. First, I've specified in the .iloprj project file to SKIP asking for references since this will be an unattended obfuscation. Yet, when I invoke, the first thing it asks is that it cannot find mscorlib, resolve or don't resolve. How do I force it to not ask me questions?

Second, if I tell leave it in default mode, it asks me to resolve several assemblies it cannot find. Yet, in the spices.net UI, it managed to find those references all by itself. How can I make the assembly that msbuild calls to obfuscate find the assemblies that are referenced all by itself? I thought it would be automatic since it's the same project file that is used in the same context.

Thanks!
Link Posted: 22-Apr-2012 02:50
First, I've specified in the .iloprj project file to SKIP asking for references since this will be an unattended obfuscation. Yet, when I invoke, the first thing it asks is that it cannot find mscorlib, resolve or don't resolve. How do I force it to not ask me questions?

Do you use AssemblyReferencesResolutionMode = Skip?

Second, if I tell leave it in default mode, it asks me to resolve several assemblies it cannot find. Yet, in the spices.net UI, it managed to find those references all by itself. How can I make the assembly that msbuild calls to obfuscate find the assemblies that are referenced all by itself? I thought it would be automatic since it's the same project file that is used in the same context.


Assembly resolution is based on SearchPaths collection, that Spices.Net automatically builds, but sometime it's not enough to find some assembly. You can review and add to SearchPaths collection (menu Edit - Option - SearchPaths property) to let Spices.Obfuscator automatically resolve references to certain assemblies.
In the case of MSBuild integration - please use SearchPaths setting of Obfuscator task to specify certain paths to automatically resolve assembly references without asking.