Comments
1 comment
-
I think you want two SmartAssembly projects (one for the Application, and another for the Plugin)
For each project SmartAssembly will scan for dependencies and you can then decide if you want to merge or embed each dependency. Merging offers the strongest protection . Please see these articles:
http://www.red-gate.com/supportcenter/C ... rtAssembly
http://www.red-gate.com/supportcenter/C ... rtAssembly
http://www.red-gate.com/supportcenter/C ... rtAssembly)
http://www.red-gate.com/supportcenter/C ... rtAssembly
I would recommend a 2 stage approach for creating your build process
1) Get your build process working manually and use the SmartAssembly application to create your project settings
If you have problems after building, please read this article:
http://www.red-gate.com/supportcenter/C ... rtAssembly
Once you are have created your two *.saproj files and you are happy with the results then you can move to automating using msbuild.
2) Automate using msbuild
Here is an article describing using SmartAssembly with msbuild:
http://www.red-gate.com/supportcenter/C ... 362558.htm
Add comment
Please sign in to leave a comment.
Depends on :
DataModel PluginsInterface Support 3rd Party Logging Apparatus
[*] DataModel[/*]
[*] Plugin
Depends on:
PluginInterface 3rd Party Logging Apparatus
[/*][*] PluginInterface
Depends on:
3rd Party Logging Apparatus
[/*][*] Support[/*]
I want to obfuscate every assembly then merge or embed the components together such that at the end of the build there should be two files:
Application Plugin
I also want to make sure I'm not including duplicate assemblies in to my final build such as the 3rd party Logging. How would I setup my MsBuild to handle this situation? Do I have to create a separate project file that obfuscates each assembly then perform the merging at the application project?