Bug 750 - Allow changing case of files/folders on case-insensitive FS
Summary: Allow changing case of files/folders on case-insensitive FS
Status: RESOLVED DUPLICATE of bug 2437
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Windows
: Low enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
: 2001 ()
Depends on:
Blocks:
 
Reported: 2011-09-11 14:18 UTC by Mikayla Hutchinson [MSFT]
Modified: 2011-12-12 12:49 UTC (History)
4 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 DUPLICATE of bug 2437

Description Mikayla Hutchinson [MSFT] 2011-09-11 14:18:15 UTC
On a case-insensitive filesystem (Windows, MacOS), when a rename of a file/folder only changes the case, that causes an error that the filename is already in use. MD could make this easier by automatically renaming the file/folder via an intermediate name: file.foo -> File.foo~tmp -> File.foo
Comment 1 Larry Ewing [MSFT] 2011-11-15 15:00:58 UTC
*** Bug 2001 has been marked as a duplicate of this bug. ***
Comment 2 Alan McGovern 2011-12-12 12:48:57 UTC
Already

*** This bug has been marked as a duplicate of bug 2437 ***
Comment 3 Alan McGovern 2011-12-12 12:49:20 UTC
That should've read: "Already fixed"