Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Names can leak, that is, property names can go into json strings or be exposed to external calls or reflection based code and dynamics.
It is all but impossible for the program to really know everything it needs to change.
We have had problems with such changes that suddenly break mvc views or javascript parsing json.
So I think they just don’t want to be the cause of breaking changes. -
@Voxera I get that but I'd rather have an option and have it warn me than not have the option at all. This is all C# code so I don't have to worry about anything like that (assuming no one is doing anything dumb with reflection)
-
@irene The same way it does when I highlight the problem spot and hit Ctrl + . then tell it to fix the naming violation
-
@Neurotrace thats the problem with leaking names. You will not get any warning. Unless you have a test case triggered you will find out in production :/
Mvc views are bound runtime and the same goes for webforms where you use databinding.
No warning until it tries to execute it.
We've introduced an official coding style at my work, which is great. Visual Studio will even alert us when code isn't up to snuff.
What Microsoft didn't think to do was let me automatically apply naming conventions across entire solutions or even just projects. I got to spend a few hours today manually going through hundreds of files and and applying the style guide.
I can automatically apply brace style across an entire solution, why won't you let me do the same with naming conventions?! A few hours down, a few more to go.
rant