Visual Studio Deployment Projects include unprotected builds
Published 03 January 2013
When using SmartAssembly with a Visual Studio Setup and Deployment Project, the MSI output may include an unprotected build of your assembly.
This can happen when you use the "project output" option to embed a file into the program files folder of your deployment project. Visual Studio retrieves this output from the project's obj subfolder, whereas SmartAssembly projects typically overwrite the output in the bin subfolder.
How to fix
To prevent this from happening, change the SmartAssembly project so that it reads and overwrites the assembly from the project's obj folder:
In Project Settings, under Selected Software, set both the original assembly and the destination assembly to the project's obj\release folder.
If you continue to experience problems, please contact Redgate support.