Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Side By Side ClickOnce Installations

I would like to deploy a TEST version of my internal application to my testing group and I need it to install side by side with the current LIVE version.

I changed everything in the Publish Options but it STILL overwrites my LIVE install. What else do I need to do? Do I have to change the Assembly Name on the Application Tab? Is that even something I should be doing? Seems like that'd break things.

Any direction on this would be greatly appreciated.

Thanks,

like image 900
Refracted Paladin Avatar asked Sep 09 '10 13:09

Refracted Paladin


People also ask

Where do ClickOnce applications install to?

Every ClickOnce application installed on a local computer has a data directory, stored in the user's Documents and Settings folder. Any file included in a ClickOnce application and marked as a "data" file is copied to this directory when an application is installed.

Is ClickOnce still supported?

ClickOnce and DirectInvoke in Microsoft Edge | Microsoft Learn. This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

What is ClickOnce installation?

ClickOnce is a deployment technology that enables you to create self-updating Windows-based applications that can be installed and run with minimal user interaction.


2 Answers

Check this out for the easy answer: http://robindotnet.wordpress.com/2009/04/22/clickonce-installing-multiple-versions-concurrently/ Short version: Change the assembly name and the Product name (so you can distinguish between the versions on the start menu).

You can muck with the deployment name, but frankly, it's more trouble than it's worth.

like image 124
RobinDotNet Avatar answered Oct 18 '22 22:10

RobinDotNet


Publishing with Visual Studio has lots of limitations. MageUI is a decent alternative as long as you are signing your deployments. Last I checked, MageUI can't create unsigned deployments.

In MageUI, all you need to change is the 'Name' field of your deployment manifest (the one with the .application extension). This should change your Application Identity and allow you to install it alongside your production version.

Another thing I've seen others do but haven't resorted to myself, is changing the assembly name. Add "Test" to your assembly name and the ClickOnce product name and it should install separately.

like image 29
codeConcussion Avatar answered Oct 18 '22 23:10

codeConcussion