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 for Bug 3210 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Currently the FIleService's purpose is not very clear.
There are methods to broadcast file change events, and methods that duplicate System.IO functionality (e.g. delete, move) but broadcast change events. These only need to be called when the VCS or project system needs to be aware of the change. Calling them in other cases is just wasting cycles.
There are some other methods for things like creating temp directories or performing atomic renames which do not broadcast events.
We need to separate them out into more clearly named classes - maybe something like ProjectFileService and FileSystemUtility - so that they're less likely to be misused.
yea, sounds like a good idea
Marking as confirmed, the issue still exists.