Effect of changing ClickOnce application publish location on clients’ machines

clickonce

OK, I have a Windows Forms application published using ClickOnce to
http://MyDevComputer1/DevPublishFolder/, so the deployement link is http://MyDevComputer1/DevPublishFolder/publish.htm.

The application is already deployed to close to 20 machines in the company intranet. I now have a requirement to change the publish location to a different server in the same network, but I'm just not sure how this change will affect the users who already have the application installed on their client machines.

How do I make sure the application detects that the publish location has been changed to a different server during the next application start up on client machines?

Or must I go and uninstall the application on all the client machines, and then re-install from the new publish location?

Best Answer

Go to the Publish tab and click the Updates button.
Add the new URL to Update Location dropdown list and click ok
Publish

Once all of the clients have received the new version, they will look to the new URL (and your new server) for all future updates.

Related Solutions

Move ClickOnce repository without reinstall in client machines. Is it possible

Here is what I have done, for people who may have the same issue.

Setup the new server on the publish package. (Project Properties, Publish Tab)
Publish to the new server
Copy the published files to the old server. (Include the .application file and the folder)

When the clients reach the old server, they will update, but the server location will be updated on the client to the new server name.

C# – How to display ClickOnce Version number on Windows Forms

Add an assembly reference to System.Deployment to your project.

Import the namespace in your class file:

VB.NET:

Imports System.Deployment.Application

C#:

using System.Deployment.Application;

Retrieve the ClickOnce version from the CurrentVersion property.

You can obtain the current version from the ApplicationDeployment.CurrentDeployment.CurrentVersion property. This returns a System.Version object.

Note (from MSDN):

CurrentVersion will differ from UpdatedVersion if a new update has been installed but you have not yet called Restart. If the deployment manifest is configured to perform automatic updates, you can compare these two values to determine if you should restart the application.

NOTE: The CurrentDeployment static property is only valid when the application has been deployed with ClickOnce. Therefore before you access this property, you should check the ApplicationDeployment.IsNetworkDeployed property first. It will always return a false in the debug environment.

VB.NET:
```
Dim myVersion as Version

If ApplicationDeployment.IsNetworkDeployed Then
   myVersion = ApplicationDeployment.CurrentDeployment.CurrentVersion
End If
```
C#:
```
Version myVersion;

if (ApplicationDeployment.IsNetworkDeployed)
   myVersion = ApplicationDeployment.CurrentDeployment.CurrentVersion;
```
Use the Version object:

From here on you can use the version information in a label, say on an "About" form, in this way:

VB.NET:
```
versionLabel.Text = String.Concat("ClickOnce published Version: v", myVersion)
```
C#:
```
versionLabel.Text = string.Concat("ClickOnce published Version: v", myVersion);
```
(Version objects are formatted as a four-part number (major.minor.build.revision).)

Best Answer

Related Solutions

Move ClickOnce repository without reinstall in client machines. Is it possible

C# – How to display ClickOnce Version number on Windows Forms

Related Topic