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 15544 [details]
Example after changing SocketRxx.cs to SocketRx.cs
I have a Xam.Forms app with a shared project. In the solution explorer if I right-click a file in the shared project and rename it then I'm seeing one of a couple different potential issues:
1. Sometimes it correctly renames the file, but if that file is open then the tab is not renamed and any continued edits to that document won't get saved to the new filename
2. Usually the file I renamed in the solution explorer doesn't change its name there, and it turns red and I can't open it (because the underlying file on the filesystem changed names). I have to remove it from the solution explorer and add it using the new name.
I tried the same thing in a PCL project and in some other projects and I wasn't able to reproduce them. But I'm able to pretty consistently reproduce this in my shared project.
Thanks so much for taking the time to submit this report! I attempted to reproduce this issue based on the bug description with the latest Visual Studio 2017 for Mac Preview version 7.2, and I was unable to hit the problem. If this issue is still occurring for you, please reopen this report and attach a reproduction, ideally starting with a new template project and then adding just the code necessary to demonstrate the issue.