ManifestManagerUtility for ClickOnce

Rating:        Based on 9 ratings
Reviewed:  4 reviews
Downloads: 10169
Released: Jun 27, 2008
Updated: Sep 17, 2010 by brumfb
Dev status: Stable Help Icon

Recommended Download

Source Code
source code, 58K, uploaded Sep 17, 2010 - 5296 downloads

Other Available Downloads

Source Code
source code, 66K, uploaded Jun 26, 2008 - 4873 downloads

Release Notes

You can publish ClickOnce applications from Visual Studio 2008 or 2010 using an SDK tool named the Manifest Generating and Editing tool (Mage) or a custom tool that uses the ClickOnce publishing APIs. Visual Studio exposes most of the capabilities needed for ClickOnce publishing. However, Visual Studio may not be available or desired for IT administrators who manage ClickOnce deployments on the server. Mage is designed to address most common administrative tasks for ClickOnce; it is a lightweight .NET Framework Windows-based application that can be given to your administrators. However, Mage requires many very detailed steps, performed in the correct order, for common tasks such as modifying the application files listed in the application manifest.

To make these tasks simpler, a custom utility is needed.

The Manifest Manager Utility sample utility here demonstrates how to use the ClickOnce publishing API to manage deployment and application manifests in a simpler way. This utility is used for updating application manifest file lists and deployment manifest settings in automated procedures for the How-to topics of the Composite Application Library.

Reviews for this release

Two stars for the effort, but this does not work reliably (at least for a .NET 4.0 app). I was able to get it to work sometimes with only one dll. But adding more than one dll gives this error after trying to install with click once: "Deployment manifest is not semantically valid."
by Vaccano on Nov 16, 2010 at 6:20 PM
This does not appear to work with .Net Framework 4
by rwrench on Jul 26, 2010 at 10:43 PM
A great application with a small flaw: the app allows you to add dlls to, for example, your Modules folder that exist in the main application_version folder but ClickOnce throws an error. Exlcuding the duplicated assemblies seems to resolve the problem.
by SSG31415926 on Aug 19, 2009 at 12:31 PM
I searched for days on how to create a custom app that will allow me to redeploy ClickOnce apps... MageUI required knowledge of how ClickOnce works, my app was going to be used by people that don't understand ClickOnce as well as I do. ManifestManager Utility hits the nail on the head and helped me figure out what I wanted to do (sorry, my app is client property, I would love to open source it!).
by krugs525 on Sep 11, 2008 at 3:52 PM