Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > Need to have my application launch at logon, replacing the explorer.exe shell
 

Need to have my application launch at logon, replacing the explorer.exe shell

Need to have my application launch at logon, replacing the explorer.exe shell. I've tried using the following to no avail...
In the following key:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell
I change the value to

C:\Documents and Settings\username\Start Menu\Programs\company\app.appref-ms

Which does not work at logon- it kicks back to explorer.exe...

I've also tried
rundll32.exe dfshim.dll,ShOpenVerbApplication C:\Documents and Settings\username\Start Menu\Programs\company\app.appref-ms

which does not load explorer.exe, but does not run the clickonce app loader.

I've tried this too, but don't recall the results other then it didn't work.

rundll32.exe dfshim.dll,ShOpenVerbApplication http://webserver/AppPublish/App.application

I can use any of the above to run the exe from command line, but not at logon.


Any help running my clickonce app as a shell replacement?
Thanks!
Jeff

Jeff C_  Wednesday, May 23, 2007 4:19 PM
I haven't actually tried very hard, but I would dearly love to hope that Microsoft's security restrictions would prevent this completely. Having your shell be an application that proactively downloads itself from the internet is a pretty scary proposition, even with code signing
Joel Bennett  Tuesday, January 15, 2008 10:30 PM
On the contrary. For enterprise and kiosk deployment, this is a reasonable hack if you don't have the money for Citrix or other expensive thin client server solutions. In the pursuit of security, with code signing and a reasonably configured web server, this solution if it worked would be just as effective as using DeepFreeze, VMware Snapshots, or scripts to restore a template workspace. The whole point in this is to keep the replacement shell, being an application in this case out of the hands of the client, effectively allowing upgrades, granted the executable does not have certain dependencies, such as shell hooks specific to explorer, or other library dependencies. It is the customer's right to be able to do this, it's completely legitimate, it's not like it'll effect other users, it's not a virus, and the concept was designed to rectify security conditions exposed by the explorer shell itself.
James R Cornell  Saturday, January 19, 2008 8:07 PM

You can use google to search for other answers

Custom Search

More Threads

• Books? Training?
• Question about Install Logs & InstallContext.LogMessage
• "another version of this product is already installed"
• Update msi install not working on vista
• Creating custom prerequisite with ClickOnce
• Adding a "enter product key to a setup "
• Deployment Problem with SQL EXpress !!
• ClickOnce error message when adding a new build
• Problems with setup project - am I thick?
• recover file