Home - Forums-.NET - Spices.Net - MSBuild integration problems

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 problems
Link Posted: 18-Jul-2006 03:42
Hi,

i'm evaluating Spices.Obfuscator 5.0.1.4 and i'm trying to automatically obfuscate an VB.NET-application using a task 'Obfuscator' in MSBuild. The syntax in my vbproj script is:


        AssemblyFile=\"D:\\Bin\\NineRays.Build.Tasks.dll\"/>


       InputFiles=\"$(OutputPath)\\$(TargetFileName)\"
     SearchPaths=\"c:\\WINDOWS\\Microsoft.NET\\Framework\\v2.0.50727\"
     Options_Members=\"234\"
     Options_Naming=\"NonDisplayable\"
     Options_Anonymizer=\"Minimum\"
     Options_MixDictionary=\"true\"
     Options_StringEncryptionMode=\"234\"
     Options_antiILDASM=\"True\"
     OutputPath=\"$(OutputPath)\" />


when i am building my project i'm getting a dialog to resolve the location of Microsoft.VisualBasic.dll. When i manual locate this dll in \"c:\\WINDOWS\\Microsoft.NET\\Framework\\v2.0.50727\" the building-process continues, but why can't it be resolved automatically???

When the obfuscator is finished i'm also getting this errormessage:

Parameter \"message\" cannot be null.
    
       at Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgumentNull(Object parameter, String parameterName)
       at Microsoft.Build.Utilities.TaskLoggingHelper.LogMessage(MessageImportance importance, String message, Object[] messageArgs)
       at Microsoft.Build.Utilities.TaskLoggingHelper.LogMessage(String message, Object[] messageArgs)
       at Q.Q._9\\u1(String )
       at \\u2.\\u168.\\u2(1 )
       at 4.\\u10.4(Project )
    

Build FAILED.


is this a bug?? The outputfiles seems to be obfuscated though.
Link Posted: 19-Jul-2006 04:50
Yes, this is a bug,
we plan to update Spices.Net assemblies today, this problem will solved in this update.
Some recommendations:
use
OutputPath=\"$(ProjectDir)Obfuscated\" />
or
OutputPath=\"$(ProjectDir)Obfuscation\" />

instead of
OutputPath=\"$(OutputPath)\" />

path as output of obfuscated assemblies if you obfuscate single assembly.
or
OutputPath=\"$(SolutionDir)Obfuscated\" />
or
OutputPath=\"$(SolutionDir)Obfuscation\" />

for obfuscation multiple assemblies.

Problem with search paths also is solved.
Link Posted: 19-Jul-2006 08:48
Fixed version is available for downloading.
Link Posted: 19-Jul-2006 20:29
Thank you very much for solving! I will try it soon, and if it works we will consider using this for our project.