Home - Forums-General - Presale and licensing questions - Problems with Evaluation Version

Presale and licensing questions

Problems with Evaluation Version
Link Posted: 28-Feb-2008 20:38
conquistadorst avatar
conquistadorst
Total Posts:0
Joined:5/3/2024
Perhaps I'm doing something very simple wrong, and if that's the case, please explain how to correct my issue.  I'm very pleased with the product so far and I am almost certain on purchasing it but I have one remaining test for Visual Studio 2005.  

Using the command line or the stand alone interface to obfuscate my dlls and executables works without a problem.  But I have issues when using VSIP.  I am following the documentation in the help file on VSIP and run into my problem.  I see the solution properties to select options for "Spices_CreateProject", "Spices_ObfuscateSolutionAfterBuild", and "Spices_ProjectFileName" and I can adjust those appropriately to enable obfuscation.  However, I do not see "Spices_IncludeToProject" or "Spices_ObfuscationOptions" when viewing the project level properties.  They are completely missing.  What am I doing wrong?  Is there some software update that I am missing?  When I do attempt to rebuild with the enabled settings at the solution level, the default obfuscation options occur but I have no way to adjust them to suit my obfuscation needs.  How do I adjust the obfuscation options from within VSIP without access to project properties?  This ability is crucial for my software deployments.  My applications are wrapped in a msi installer package that will require obfuscation prior to being wrapped.  How do I make this work?

Thank you for your help.
Link Posted: 29-Feb-2008 03:20
NineRays avatar
NineRays
Total Posts:0
Joined:5/3/2024
Some Visual Studio project types don't support extension of their properties.
In that case you can use more convenient way for VS2005/VS2008 - use MSBuild integration of Spices.Net.
See the documentation (Spices.Obfuscator\MSBuild integration chapter and topics) how to embed Spices.Obfuscator tasks into your project.
Link Posted: 29-Feb-2008 16:39
conquistadorst avatar
conquistadorst
Total Posts:0
Joined:5/3/2024
Thank you for the tip, I will try that and report back on my results.
Link Posted: 29-Feb-2008 19:14
NineRays avatar
NineRays
Total Posts:0
Joined:5/3/2024
If you have any question or problem, please feel free to contact us for further assistance.
Link Posted: 03-Mar-2008 19:06
conquistadorst avatar
conquistadorst
Total Posts:0
Joined:5/3/2024
I have been trying to apply your suggestions and have had some success but I have still been unable to achieve my final goal.  I can now indeed apply MSBuild operations to obfuscate an executable using the "BeforeBuild" and "AfterBuild" events.  However my Visual Studio Deployment Project is not picking up the correct version of the obfuscated executable.  By its configuration it appears the project is expecting to grab the executable from my project's "obj/Release" folder however when I point my "BeforeBuild" or "AfterBuild" output path to that folder it seems to be automatically overwritten and perhaps never used.  Pointing "OutputPath" to a different folder works fine but I need to include my obfuscated *.exe into the final *.msi package I am producing.  

What MSBuild events, parameters, or settings do I need to implement in order to get this working?  Your documentation does not go into the sort of detail I am looking for.  Please let me know if you need additional information about how my project is configured.  Thank you.
Link Posted: 03-Mar-2008 20:50
NineRays avatar
NineRays
Total Posts:0
Joined:5/3/2024
To obfuscate assemblies to the place of original assemblies just don't specify SaveToDirectory parameter.
But I would recommend you to obfuscate assemblies to certain folder (Obfuscated for example) or copy original assemblies to certain folder (Original for example) before obfuscation to keep original assemblies for debugging/diagnostics.
Link Posted: 04-Mar-2008 16:11
conquistadorst avatar
conquistadorst
Total Posts:0
Joined:5/3/2024
I don't think you are understanding my problem.  I do not have a problem with the locationof obfuscated assemblies.

I am trying to use the obfuscated assemblies to create my attached Visual Studio Deployment Project.  How do I do this?  This is not explained in your documentation.
Link Posted: 05-Mar-2008 03:19
NineRays avatar
NineRays
Total Posts:0
Joined:5/3/2024
Yes, may be I don't clearly understand your problem, please explain it more detailly.
Usually, when you've specified folder for obfuscated assemblies, you should simply include assemblies in that folder to your deployment project.
If your problem relating to updating application and deployment manifest after obfuscation, you can use mage utility (.Net SDK including that utility) in your MSBuild script to update these manifests.
Link Posted: 11-May-2008 19:32
conquistadorst avatar
conquistadorst
Total Posts:0
Joined:5/3/2024
Thank you, I forgot to come back here and tell you your solution worked for my needs.  Not my idea of the cleanest solution, I'd much rather be able to do everything from a UI, but utilizing msbuild is fair enough.
Share:

Company  |  Privacy  |  Legal Information

© 1999-2024 9Rays.Net. All rights reserved.