Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 1577 [details]
sequence of events...
If I edit a file, close it, and then open it again MonoDevelop will generate an error message indicating that the file was closed without saving. I have attached an image that illustrates the steps. I am using OSX 10.7.3 Server edition.
1) Edit the file ExtensionFactory, notice how the file appears modified.
2) Save the file, notice how Monodevelop does not put the changed status on the file.
3) Close the file using the close icon on the tab (but you can close via the menu as well).
4) Open the file again and notice how Monodevelop will come with an error indicating "An autosave file has been found for this file."
IF I load either choice from message, and then close it, and open it again no message. Thus this occurs only if you edit a file.
This bug is downright annoying and makes Monodevelop quite unusable...
This was fixed after 2.8.6 was branched, and not backported. It should be resolved in 2.8.8 (currently in beta).
*** This bug has been marked as a duplicate of bug 1455 ***