ClickOnce

ClickOnce deployment solves a number of maintenance and logistics issues, while adding a few new concerns.  No longer does a warm body need to run around updating PCs.

But how do you update and track various versions?  The manifest contains information about a specific version of a ClickOnce application and the various supporting assemblies in a human readable XML format.  The "assemblyIdentity" element specifies the primary assembly for the application while the "dependency" element lists all the prerequisites assemblies.

The manifest is also accompanied by a precompiled manifest named *.CDF-MS.

Walkthrough: http://msdn.microsoft.com/en-us/library/xc3tc5xx(VS.80).aspx


Look into using MSBuild to publish the ClickOnce to the Web.
http://msdn.microsoft.com/en-us/library/ms165431(v=vs.80).aspx

For concurrent deployments, make sure to change the assembly name and product name.

http://robindotnet.wordpress.com/2009/04/22/clickonce-installing-multiple-versions-concurrently/