clickonce

Is it possible to deploy a Windows Service using ClickOnce? If so, how do you achieve this? Currently we have to use a Deployment project, and the installation process could be simplified greatly by using ClickOnce. Marc Gravell AFAIK you can't really use ClickOnce end-to-end to deploy a service; there are issues with both the file locations (ClickOnce installs into a user's profile) and installation (ClickOnce is largely side-effect free). You can, however, write a service as an exe that can self-install/uninstall from the services list, like so ; basically, you write it as as a console exe

I have a collection of ClickOnce packages in a publish folder on a network drive and need to move them all to another server (our DR machine). After copy/pasting the whole directory and running the setups on the new machine I get an error message stating that it cannot find the old path: Activation of ...MyClickOnceApp.application resulted in exception. Following failure messages were detected: + Downloading file://oldMachine/c$/MyClickOnceApp.application did not succeed. + Could not find a part of the path '\\oldMachine\c$\MyClickOnceApp.application'. Once I change the installation URL to

How can I make a Click-once deployed app run a startup? The best option I found by searching was to set the Publisher on the app to Startup, so the Start menu shortcut would be placed in the Startup folder, but that seems like a huge hack and I would like there to be a Start menu icon people can find. What options do I have? Don Scott I feel that adding your application to the startup folder is unprofessional. I strongly recommend using a startup registry key to launch your application. Contrary to what a lot of the material on this topic says, it is extremely simple to setup a key to launch a

I would like the ability to have a test ClickOnce server for my applications where users can run both the production version and the test version in parallel. Is this possible? I first tried using the following in AssemblyInfo.cs and also changing the name in the ClickOnce deployment though all this achieved was overwriting the users' production version with the test version. Likewise, it did the same when they went back to the production server. #if DEBUG [assembly: AssemblyTitle("Product Name - Test")] #else [assembly: AssemblyTitle("Product Name")] #endif I thought I should also clarify

How to I configure click-once to install apps for all users. On another forum I got to 'use MSI' - thanks - but how. Also, the first installing user may not be admin - which may be a problem. And I want all users to trigger an update check. No local storage, it's a WPF client to a WCF service. We're XP, internal. If you need to install / upgrade for all users on a PC, Clickonce is not an option. Clickonce is meant for installing an application for a single user without administrative rights. You will need to create a MSI installer to distribute an application to multiple users on the same