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.
1. Open an .NET Core project that implicitly builds its <Compile> nodes (<Compile Include="**\*.cs"/>).
2. Perform a rename _outside_ of VSM (e.g. a git mv) of one of the files in an expanded directory.
3. (notice that the folder does not update automatically, which is a completely separate issue)
4. Right click on the folder in VSM that contains the renamed file and choose "Refresh"
5. Notice that the old file name is still in the tree, but is now red, because it no longer exists
-> expected: this node should have been removed
6. Notice that the new file name does not appear at all
-> expected: a new node should be added for the new/renamed file
There is a dotnet-file-watcher feature branch which will support this by automatically handling renames done outside of VS Mac. It is currently targeted for 15.6 but has not been approved by QA yet.
Fixed in 15.6
Merged in master (VS Mac 7.5):
Merged in d15-6 (VS Mac 7.4):