Visual studio 2008 setup project create desktop shortcut

Zipped file is attached. Comments or Responses. Login to post response. Straight to Experiment First of all create a blank solution and add a Windows form project. Next add a "Setup and Deployment" project. The shortcut appear below the primary output which is the application executable Right click on the "Shortcut" and Rename it to "MyWindowsFormsApplication".

Build the application and install it. Give a name to your shortcut like 'My Application Name' and press 'Finish'. Now you will have a shortcut that can be copied to other machines if needed. You can also right-click the new shortcut and change the icon if you want too. As for preventing users with the.

NET Framework versions less than 2. If this is a web app it will be hosted on a server and use its installed framework. Usually you don't get into problems with incompatible frameworks until you being building windows applications where the clients machine's framework is used.

Regardless, if there was a Framework issue, the web app when launched would display an error stating there were Framework issues. For this, i create a url shortcut of my application and set an icon for my shortcut and add it to user's desktop folder in my web setup project. The content you requested has been removed. Ask a question. Quick access. Search related threads. Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search.

I have a Visual Studio Setup Project that creates desktop and startup menu shortcuts during the install. The shortcuts created invoke the application if user clicks on them. However, the shortcuts cannot be used as a drop target. Also, the shortcut also cannot be used via SendTo command from Explorer. If you check properties of the shortcut from Explorer, the Target has just the application name and is grayed out for example, MyApplication. In the manually created shortcut, the Target has full path to the application i.

Other settings are the same. I suppose that this intermediate executable is intended to provide some installation integrity check or something like this. The Icon location is also re-directed to this executable.

While the intend may have been good, as I mentioned above, this seems to prevent the shortcut from being recognized as drop and sendto targets. Is there a way to tell the installer to create shortcuts to the actual target and not the intermediate exe?

I guess the coder of the Setup Project Shortcuts took a shortcut here… I currently just let the installer install whatever it wants and then in the post install action modify the installed shortcuts and manually install the sendto shortcuts for all users as outlined above.

This works but I was wondering if there is a cleaner solution to both of those issues. I use the following script to tell VS to create "regular" shortcuts.