Bug 1663 - Should auto-rename old License.v2 file when upgrading to MT5
Summary: Should auto-rename old License.v2 file when upgrading to MT5
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 5.0
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2011-10-24 16:25 UTC by Jeffrey Stedfast
Modified: 2011-11-11 15:55 UTC (History)
1 user (show)

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:

Description Jeffrey Stedfast 2011-10-24 16:25:44 UTC
A customer on IRC #monotouch noted to me that when he upgraded to MonoTouch 5.0 from an old install of MonoTouch, that it failed due to the old license file being in the way and that it took him a while to figure out how to fix that issue.

He suggested that we document that users upgrading should move that license file out of the way first, but I think we should do better: we should auto-rename that file (License.v2.bak?) or ask the user or something, we don't want to require our users to have to dig up documentation on these sorts of failures.
Comment 1 Jeffrey Stedfast 2011-11-11 15:55:51 UTC
Going to consider this fixed now unless we get actual specifics.