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

Question

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 d

Answer 1

For each environment, keep separate assembly names and product names with a postfix of the environment name. In addition, create a GUID for each environment, and add it to the AssemblyInfo.cs, for example:

[assembly: GuidAttribute("FA380FBE-11B0-406E-88D3-AF40BE93F7D6")]

This then makes it possible to run the same application from separate ClickOnce sites, each having a short cut corresponding to the product name.