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?
Thanks DiscDev and dbenham. The solution works great. Just wanted to share the updated working code based on the latest by dbenham.
After reading all the comments on this thread and the johnnycoder blog post mentioned above, I came up with a solution that:
My Solution
Basically, your app will be writing a
.bat
file to the Startup folder that launches the ClickOnce app for you. The.bat
file is smart enough to detect if the app has been uninstalled and will delete itself if the ClickOnce app cannot be found.Step 1
Get the batch file working. Replace PUBLISHER_NAME and APPLICATION_NAME with the right values. You can find them by installing your ClickOnce app, then following the path to it on your file system:
The batch file will check if your ClickOnce app is installed (by seeing if the appref-ms file exists) and launch it if so. Otherwise, the batch file deletes itself, via a method outlined here.
Now that you have the batch file, test it out. Drop it in your Startup folder to make sure it launches your app on login.
Step 2
Now, in the code for your app, you need to write this batch file to the Startup folder. Here is an example using the batch file above in C# (note that there is some escaping, and environment variable voodoo happening):
There you have it. Comments / improvements welcomed.
EDIT: Fixed quotes in step 2
For some reason, windows wouldn't start my app (the ".appref-ms" file) when logging in. So, I came up with a solution others might find helpful as well.
When my app is installed for the first time (and on start up of my app), I add/verify that my applications current location
string.Concat(Application.ExecutablePath, " ", "/startup")
exists in the registry"HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run"
. When the application then starts, I check the args for "/startup" and if that is present, execute the following code.This worked great for me. But, if you just add the
Application.ExecutablePath
value to the registry without the"/startup"
arguement, the application will start when windows starts but not in the context of a "click once" application. This will not allow you to have access toApplicationDeployment.CurrentDeployment
. Although, this worked great, the problem still exists that when my application is uninstalled, the registry setting isn't removed. This can be fixed by using @Ivan Leonenko custom uninstall solution. Hope this helps...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 click once application and does not require setting up additional shortcuts. You simply use the shortcut created on install:
I make this and work for me
Well there're a number of ways to make your application launch on start up, but there's a clean up problem. Even if you use start up registry key and it looks fine, anyway you should clean all you added to thesystem. You can take a look on my article, I faced same clean up problem and used automation and cutom uninstall file to solve issue.