Hello,
I have some general questions about ClickOnce. Before VS2005 I used ZeroDeployment under .NET Framework 1.1! Our customers liked the way of central installation on a server.
Now, with ClickOnce, I published my Application in a local directory on my laptop. Then I added the published files to an Setup Project.
When I now install this Setup on a customer server and I start the Setup.exe from a client, I get the error message, that the location \\xyz\Click Once could not be found.
Can I use the ClickOnce in this way, or do I have to return to the normal MSI way
Thx for help
John
I need help with ClickOnce
GaneshParam
John,
The good news is, yes you can use ClickOnce this way. If you are publishing for Visual Studio just set the installation URL to be either a UNC path on a server accessible from everywhere, or a URL on a web-site. You can then have the click-once deployment built to a local share on your laptop and then copy it to the relevant location central share or web server.
If you use ClickONce in this way you will not need a setup project.
Hope this helps,
David
allsoppg
John,
If you want to send CD's to customers then you will need a setup project, although if you have a publically accessible website it may be a better option to use Click-Once for them too - that way you can give them updates automatically (or indeed enforce updates if you wish).
For your internal updates have a look at the "Publish" tab in your project properties. The box labelled Publishing Location should be the directory on your laptop where Visual Studio will actually put the files. The box labelled Installation URL can be either a fileshare on your server or an internal URL. All you need to do after you've hit the Publish Now button is copy the files from the Publishing Location to the Installation Location.
After you've run a publish in Visual Studio it will automatically popup the installation page. If you're publishing to somewhere other than the installation location you should ignore this as it will be pointing at an old version until you've copied the files across.
That should look after your internal users, but you can't use the same updates for your customers unless you can publish to a location accessible to them. If you have no way of making files available to them other than by sending CD's you'll need to use a setup project, but make sure that the setup project isn't trying to package up your Click-Once deployed application. The best way is to put your code into an assembly and then have a Click-Once deployed application that calls it for local users, and a standard Windows.Forms application deployed by Setup project for other users.
Fazi
Hello David,
thanks for your fast answer, but I still got some questions...
I did not really understand what you mean, but I am publishing on a local shared directory. From there I copy the files on a server but then there is the puplish location written in the application.manifest. And that is the problem.
I am using the Setup only for distributing the ClickOnce-files on a CD for our customers.
Well, when you still think that it works, then please discribe me how I must configure VS2005.
Many thanks
John