Style Cop
-
I started to check out StyleCop this morning. I'm not going to rant about every other rule it follows, but has anyone noticed that the file **.Designer.cs violates:
SA1201: All methods must be placed after all fields.
Windows creates this file. I think I'm done with StyleCop.
Is that the latest incarnation of FXCOP? Perfect tool if you want lots of criticism of perfectly valid code if so.
Regards, Rob Philpott.
-
I never understood the need to for formatting software (I think that is what StyleCop is right?).
Not so much formatting as code styles and guidelines, like variable naming, comments, order of fields, methods etc.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
I never understood the need to for formatting software (I think that is what StyleCop is right?).
-
Is that the latest incarnation of FXCOP? Perfect tool if you want lots of criticism of perfectly valid code if so.
Regards, Rob Philpott.
No, FxCop and StyleCop are different. StyleCop analyzes your source code, whereas FxCop does static analysis on your compiled assembly. Normally you are supposed to use them together, so they complement each other.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
It was recommended to me in a previous post regarding a coworker's use of under_score instead of underScore in the middle of variables. Someone recommended that I try StyleCop to settle our convention disputes.
You really don't need a tool to police that. The accepted convention is camel case for variables, so under_score is simply wrong. Suggest (s)he reads a book or something.
Regards, Rob Philpott.
-
No, FxCop and StyleCop are different. StyleCop analyzes your source code, whereas FxCop does static analysis on your compiled assembly. Normally you are supposed to use them together, so they complement each other.
Regards, Nish
My technology blog: voidnish.wordpress.com
Oh, ok. In which case, I hate *both* of them.
Regards, Rob Philpott.
-
Oh, ok. In which case, I hate *both* of them.
Regards, Rob Philpott.
-
It was recommended to me in a previous post regarding a coworker's use of under_score instead of underScore in the middle of variables. Someone recommended that I try StyleCop to settle our convention disputes.
How about the MS Naming Guidelines[^]??
Sarchasm : The gulf between the author of sarcastic wit and the person who doesn't get it.
-
I never understood the need to for formatting software (I think that is what StyleCop is right?).
I sometimes feel alone in this opinion, but I believe that source code readability is a very, very, close second place to code correctness. Anyone else?
"Why look within yourself for THE TRUTH, when you're the one who's confused in the first place?" Mr. Spackle
-
I started to check out StyleCop this morning. I'm not going to rant about every other rule it follows, but has anyone noticed that the file **.Designer.cs violates:
SA1201: All methods must be placed after all fields.
Windows creates this file. I think I'm done with StyleCop.
-
You really don't need a tool to police that. The accepted convention is camel case for variables, so under_score is simply wrong. Suggest (s)he reads a book or something.
Regards, Rob Philpott.
Rob Philpott wrote:
The accepted convention is camel case for variables, so under_score is simply wrong.
That is your opinion. Microsoft begs to differ with their internal coding practices. I thought we killed this bird a few days ago.
-
I sometimes feel alone in this opinion, but I believe that source code readability is a very, very, close second place to code correctness. Anyone else?
"Why look within yourself for THE TRUTH, when you're the one who's confused in the first place?" Mr. Spackle
me too. which is why i think LINQ is crap.
-
Rob Philpott wrote:
The accepted convention is camel case for variables, so under_score is simply wrong.
That is your opinion. Microsoft begs to differ with their internal coding practices. I thought we killed this bird a few days ago.
Mine and everyone else I know - yes.
Regards, Rob Philpott.
-
Not so much formatting as code styles and guidelines, like variable naming, comments, order of fields, methods etc.
Regards, Nish
My technology blog: voidnish.wordpress.com
Thanks for the correction. :)
-
Thanks for the correction. :)
-
Mine and everyone else I know - yes.
Regards, Rob Philpott.
Since you like it, what's the rationale for starting just the first word with a lower case letter? Why is
customerAccountNumberbetter thanCustomerAccountNumberorstrCustomerAccountNumberorlpszCustomerAccountNumber? -
Since you like it, what's the rationale for starting just the first word with a lower case letter? Why is
customerAccountNumberbetter thanCustomerAccountNumberorstrCustomerAccountNumberorlpszCustomerAccountNumber?Who knows? The point is convention. You can tell at a glance what you're dealing with (local/member/property etc). And if we all do things the same way it makes it easier to understand each other's code. A good thing surely.
Regards, Rob Philpott.
-
StyleCop is meant to be used on user-written source files. Do not use it on auto-generated files :-)
Regards, Nish
My technology blog: voidnish.wordpress.com
Hmmm, I always thought StyleCop was intended for the garbage can...
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Who knows? The point is convention. You can tell at a glance what you're dealing with (local/member/property etc). And if we all do things the same way it makes it easier to understand each other's code. A good thing surely.
Regards, Rob Philpott.
Rob Philpott wrote:
Who knows? The point is convention.
And that's my point. All you're saying is that being consistent is good, and being able to identify scope from name is good. But that's not a justification for using camel case. I've never seen a good reason why it's "better" than other naming standards, and I think it's worse. My deliberately chosen example is something that is conventionally called a number, but in the real world is very ofen a mixture of letters and numbers, and so has to be represented as a string. Using the camel case standard, you somethings can't infer data type from the name, which to me seems a backward step.
