Bug 946 - When updating a MonoDevelop.app that has been renamed, we should offer the option to install the renamed version
Summary: When updating a MonoDevelop.app that has been renamed, we should offer the op...
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Updater ()
Version: 2.8 Beta 2
Hardware: Macintosh Mac OS
: Low normal
Target Milestone: (C7)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-09-20 17:58 UTC by Alex Corrado [MSFT]
Modified: 2016-05-13 14:58 UTC (History)
6 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:
VERIFIED FIXED

Description Alex Corrado [MSFT] 2011-09-20 17:58:01 UTC
Environment:
 + Mono 2.10.6
 + Mac OS Lion 10.7.1
 + MD 2.8 beta 2
 + Mono for Android Eval 1.0.3
 + MonoTouch 4.0.4.1

To Reproduce:
Let MonoDevelop check for updates and it should report updates for MonoTouch 4.2 and Mono for Android 1.2 are available.

Click the Update button. Nothing happens.
Comment 1 Alex Corrado [MSFT] 2011-09-20 19:13:31 UTC
After messing with this some more, it looks like it breaks when you rename MonoDevelop.app. Naming it back causes the updater to launch as expected.
Comment 2 Miguel de Icaza [MSFT] 2011-09-21 15:33:42 UTC
CCing Lluis to this bug so he can weigh in
Comment 3 Chris Hardy [MSFT] 2011-09-25 15:47:26 UTC
I'm hitting the same issue here and so are a few of our users since having multiple instances of MonoDevelop is normally required (or having multiple versions of MonoDevelop are needed to be installed side by side). This is probably going to be a common issue.

I hit the same issue on MD 2.8 beta 3 too, except from it closes MonoDevelop but installs nothing.
Comment 4 Alex Corrado [MSFT] 2011-09-25 16:57:58 UTC
It sounds like we've confirmed that renaming the app bundle is the cause, so I am making the title of the bug a little more specific.
Comment 5 Miguel de Icaza [MSFT] 2011-09-27 10:13:11 UTC
Michael reports that this is caused by a sanity check on the updater.

As discussed on the call this morning, we should change the sanity check.

The other bit will be to handle the case where users renamed MonoDevelop.app to MonoDevelop28.app for example.   In that case, instead of replacing MonoDevelop.app in place, it would open the folder, and let the user do the update himself or renames as he sees fit.
Comment 6 Mikayla Hutchinson [MSFT] 2011-09-30 12:48:00 UTC
Fixed the sanity check.

The renamed MonoDevelop.app will be harder.
Comment 7 Miguel de Icaza [MSFT] 2011-10-04 10:58:40 UTC
Current situation:

If we rename MonoDevelop.app to MonoDevelop28.app, if we get an update for 2.8.1, it would delete MonoDevelop28.app and replace it with MonoDevelop.app

We want to fix this scenario.
Comment 8 PJ 2013-11-19 16:32:22 UTC
This bug was targeted for a past milestone, moving to the next active milestone.
Comment 9 iain 2015-10-06 07:02:16 UTC
This appears to work now.