Safely publishing a ClickOnce application with the Manifest Manager Utility

Topics: Prism v4 - WPF 4
Mar 22, 2011 at 10:07 PM

When using the Manifest Manager Utility to add DLLs to the application manifest and then resign the application manifest, how do you eliminate the risk of version update problems caused when a user launches the application before the Manifest Manager step is completed?  In Visual Studio I'm using the ClickOnce automatic update option, the application is available offline, and the application is being pubished to a file share.  Would it be safest to temporarily restrict permissions on the file share until the publish is completed?

Mar 23, 2011 at 6:22 PM

Hi,

Since this topic is not strictly related to Prism, you might find better support in the ClickOnce Setup & Deploy Projects forum.

Thanks,

Miguel Bronzovic
http://blogs.southworks.net/mbronzovic

 

Mar 23, 2011 at 10:15 PM

Prior to posting here, I posted in the ClickOnce Setup & Deploy Projects forum.

In that forum RobinDotNet has provided an answer.  The solution is to publish to a work directory structure (i.e. not the deployment file share).  When you're done using the Manifest Manager Utility, copy the version folder (yourapp_x_y_b) to the "Application Files" folder in the target directory structure (in my case the file share).  Then copy the deployment manifest (.application) and setup.exe in the top folder to the top folder in the target directory (root folder of file share).