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.
This might be too difficult to get right, but it Xamarin Studio knows enough about C# it seems when I rename a method, that it would go through the full project (over all files) and do the rename everywhere. It only seems to apply the rename to the current file.
I just did a refactor -> rename and right after a few places (in different files) broke because they were still going for the old name. Seems to me it ought to be possible to figure out who is referring to the method or property, etc. and snake the rename over all files.
Good luck! :)
Yes, rename does rename across all files. Maybe there's something about your project or environment that's breaking this. Are there any errors in the log file (Help->Open Log Directory) after such a rename? Does this fail for new projects too, or just your existing project?
Which version are you using ?
5.1.3 (build 0)
Ok that should work.
Can you reproduce the problem ?
Actually -- no. I can't at the moment. I'll keep an eye out for it though. Unfortunately I don't rename things all that much. But next time it happens, I'll let you know. Just tried a few times, and it worked across files.
The next time try to open the log directory.
I think that an error has happened somewhere. I'll close that one because I can't really fix something that's not reproduceable without error :/