How do I build deployment project without un-signing my assemblies?

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!


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.

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.

Need Your Help

Can you change the behavior of Out-Default for a script?

powershell powershell-v2.0

I have a script with a series of Invoke-Command statements, and each one has code on the end writing out to a file. Can I simply change the behavior of Out-Default temporarily and clean up my scri...

Get characters of a string (from right)

python string

I'm looking for the best way to get a file name of a variable that looks like that:

About UNIX Resources Network

Original, collect and organize Developers related documents, information and materials, contains jQuery, Html, CSS, MySQL, .NET, ASP.NET, SQL, objective-c, iPhone, Ruby on Rails, C, SQL Server, Ruby, Arrays, Regex, ASP.NET MVC, WPF, XML, Ajax, DataBase, and so on.