Multiple ClickOnce installations with different Deployment Identity, but same Application Identity

clickonce
Karg picture Karg · Jul 30, 2009 · Viewed 19.7k times · Source

We have several deployments of the same assemblies with different configuration files for different environments. We package these up in to separate ClickOnce deployments with different Deployment Identities (Program_ENV1, Program_ENV2, etc.).

The Application Identity is Program.exe for all of them, because we have a third-party component that requires the executable using it to have the same name as it was compiled for.

When we want to have multiple installs of the same version number on the same machine (for testing), we get an error on installation that something with the same application identity already exists.

We don't want to make separate builds with new version numbers for each deployment (QA signed off on version X.X.X.45 assemblies, not version X.X.X.46).

Is there another way around this issue?

Answer

RobinDotNet picture RobinDotNet · Aug 21, 2009

To run concurrent versions of a ClickOnce application, you must change the AssemblyName, and it's recommended that you also change the ProductName in the Publish properties, so you can tell in a start menu which one is which.

Click here to see how to Install Multiple Versions Concurrently

Related questions

How to get folder path for ClickOnce application

I need to write a file in the same folder where a console ClickOnce .application (executable file) resides. The folder where it launches from. I tried using Application.StartupPath & Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location) but the path is pointing …

Read More
Best way to deploy Visual Studio application that can run without installing

I wrote a fairly simple application with C#/.NET and can't figure out a good way to publish it. It's a sort of a "tool" that users would only run once, or run every few months. Because of this, I'm …

Read More
Error message "Unable to install or run the application. The application requires stdole Version 7.0.3300.0 in the GAC"

When one user tries to run the application, our ClickOnce application is reporting: Unable to install or run the application. The application requires stdole Version 7.0.3300.0 in the GAC. It's interesting to note that the GAC (C:\Windows\assembly) does not …

Read More