Bug 7202 - Externally removed file silently dissapear in editor
Summary: Externally removed file silently dissapear in editor
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Management ()
Version: Trunk
Hardware: PC Linux
: Normal normal
Target Milestone: (C7)
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-09-16 16:37 UTC by Peter Hultqvist
Modified: 2016-05-19 15:15 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:
VERIFIED FIXED

Description Peter Hultqvist 2012-09-16 16:37:17 UTC
If an opened file is removed from disk using an external program it will silently close that file even if there are unsaved changes.
Comment 1 Peter Hultqvist 2013-03-11 04:21:16 UTC
Tested again, same result for current master(past xs-4.0.2)
Comment 2 xamarin-release-manager 2016-01-20 08:12:29 UTC
Fixed in version 6.0.0.3013 (master)

Author: Mike Kr??ger
Commit: 27006b8c8d682e981ec1e300ba3d6275207294d7 (mono/monodevelop)
Comment 3 Abhishek 2016-05-19 15:15:53 UTC
I have checked this issue with latest C7 build:
XamarinStudio-6.0.0.5165_b44eb696fa41a04696a84d6af7fed9aa494e5580. Now this issue is working fine. Here is the screencast for the same: http://www.screencast.com/t/JqZdgPIal

Hence closing this issue.

Thanks!