I'm not very experienced with builds - this may be really easy! I have a simple application with a simple deployment project. I went to the directory where the release-compiled versions of the DLLs are, signed all of them (verisign), and then went to the deployment project, chose Build (not REbuild), and it recompiled all my assemblies and now they aren't signed any more. Can I keep the nice easy deployment project and still have signed assemblies, or do I have to create the MSI a different way? Thanks!
+1
A:
I haven't tried, but... Don't make the deployment project depend on the application project. Instead, manually add the output of the application to the deployment. As a consequence, no automatic build should be triggered.
Martin v. Löwis
2008-11-18 23:56:00
This was the answer for me.
Gregory
2009-10-10 22:26:05
A:
Try signing the assemblies as an intermediate step of your build.
One way to do this is to add a dummy project that has a build event that signs your assemblies. Make this project the last step before you create your MSI package.
Jason Slocomb
2008-11-19 00:14:48