Bug 4201 - Create a new class, then change the name of it *before* commit
Summary: Create a new class, then change the name of it *before* commit
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
URL:
Depends on:
Blocks:
 
Reported: 2012-04-03 04:55 UTC by John Hair
Modified: 2012-04-11 10:51 UTC (History)
1 user (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 John Hair 2012-04-03 04:55:25 UTC
MD 2.8.6.5
Created a new class, then decided to rename it by right click in solution explorer. The original file was not deleted. When I came to commit all changes to SVN it still wanted to commit the originally created file and not the renamed version. So I excluded the original file from the solution and added in the renamed file.
Come to commit, it *still* wants to commit the renamed file which I have now deleted. So I can no longer commit. (workaround easy, just restore the deleted file, commit and delete it after).
Comment 1 Alan McGovern 2012-04-11 10:51:04 UTC
This has been fixed already. You'll need to update to MonoDevelop 2.8.8 or higher. Thanks for reporting this!