Bug 11466 - Source view (VS2010): undo command deletes entire file
Summary: Source view (VS2010): undo command deletes entire file
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android Designer ()
Version: unspecified
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
: 19350 ()
Depends on:
Blocks:
 
Reported: 2013-03-28 15:12 UTC by Adam Patridge
Modified: 2017-07-07 14:15 UTC (History)
8 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 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 Adam Patridge 2013-03-28 15:12:32 UTC
Steps to reproduce:
1. Open or create new layout .axml file in Visual Studio 2010.
2. Switch to Source view.
3. Undo and entire file contents disappear.
[4. Redo and contents reappear but file still says it is modified.]

This happens whether you make any changes or not. The last undo command will consistently delete the file's entire XML contents.
Comment 1 Lluis Sanchez 2014-05-08 12:16:23 UTC
*** Bug 19350 has been marked as a duplicate of this bug. ***
Comment 2 Pierce Boggan [MSFT] 2017-07-07 14:15:03 UTC
Thanks so much for taking the time to submit this report! I can confirm I am no longer able to reproduce this issue using the latest Visual Studio 15.3 preview builds. Marking this report as RESOLVED. :)