This looks very promising, especially where an application does not need to deploy any files to the GAC (Global Assembly Cache). An example of .Net applications that deploy to the GAC would be those that use Microsoft Office PIAs (Primary Interop Asseblies)
However, there may be work arounds for this, such as installing PIA's separately.
This page gives a good walk through of ClickOnce deployment.
In visual studio, Build\Publish takes you to the simple publishing wizard.
When you publish, a set of folders and files is created that inclused Publish.htm.
This is the starting point for installing the ClickOnce application on the user's PC.
When choosing the local web server screen shot one shows the resulting folders\files that are created.
Opening Publish.htm gives this screen:
Click Install and this dialog follows:
As in my test scenario the application was not signed, this dialog appeared.
The application is not actually stored on the client machine. (At least not in the usual location, it is not is program files sub directory)When an update is posted to the update location, and a user clicks on the application shortcut they will see this message. Note, the update has it's own version number system, and does not depend on the application version number.
Deploying ClickOnce Solutions On Client Sites
In the project properties\publish tab there are options that can be set that make it possible to have install and update locations that are different from the publish location.
On the main page there is an installation URL as well as a publish URL. Make the installation URL the location of the files on the client site. On the Update page, set the Update Location to the place on the client network where updates will be located. This can be the same as the publish URL.
No comments:
Post a Comment