Bug 12285 - Every time an update is applied, my Xamarin shortcut on the desktop is made invalid
Summary: Every time an update is applied, my Xamarin shortcut on the desktop is made i...
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Installer ()
Version: 4.0.6
Hardware: PC Windows
: --- normal
Target Milestone: master
Assignee: Marius Ungureanu
URL:
Depends on:
Blocks:
 
Reported: 2013-05-17 12:15 UTC by Jim O'Brien
Modified: 2015-08-27 09:40 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Jim O'Brien 2013-05-17 12:15:32 UTC
Every time Xamarin Studio is updated, the shortcut (built using 'Send To' via 'All Programs') gets corrupted and I must delete the corrupted one and rebuild.

I have had to do this 3 times since I installed Xamarin 3 days ago.

To say the least, it is a bit annoying.
Comment 1 Marius Ungureanu 2013-06-19 04:39:50 UTC
The corruption consists of the shortcut linking to:
"C:\Program Files (x86)\Xamarin Studio\bin\"

Aka, the XamarinStudio.exe is trimmed.
Comment 2 Marius Ungureanu 2015-08-27 09:40:07 UTC
No longer an issue in 5.10.