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.
The fix is not correct AFAICT as it will turn things like Net_1_1 into Net11, where they should be turned into Net1_1.
What does reshaper do with Net_1_1 ?
Dunno, but converting "1_1" (which probably meant "1.1") to "11" is nonsensical - 1.1 != 11. That's why I had that check in there.
Net1_1 is not a name according to .NET naming guidelines. This kind of formatting wasn't specified - and therefore it's ok to the rules to warn about that.
I checked with R# - they do the same.
For things like that use:
// Resharper disable InconsistentNaming
// Resharper restore InconsistentNaming
And no - we shouldn't change the .NET naming guidelines - there are just some exceptions to the 'golden rules' - that's what issue suppression is for.