Naming Question

[Tim Groven]

Probably a dumb question, but where can I find the Microsoft guidelines for this? :(

[Lost User]

Caydence wrote:

Probably a dumb question

It's not, but I'm glad to see that you rather make a "dumb" impression and get an answer than look intelligent and move on without one. Here they are[^] :)

Bastard Programmer from Hell :suss:

[Lost User]

Did you used to have lots of lngFilename or blnFilenames as well? ;P

Bastard Programmer from Hell :suss:

[Lost User]

fileName and filenameAndPath. Meh.. ..is that with or without extension? A UNC-path, or local?

Bastard Programmer from Hell :suss:

[Tim Groven]

I don't mind admitting I don't know something. :)

[Pete OHanlon]

Then just filename. It's a standard concatenation and MS is fairly clear on naming for contractions like this; all lower case.

Forgive your enemies - it messes with their heads

"Mind bleach! Send me mind bleach!" - Nagy Vilmos

My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility

[PIEBALDconsult]

Eddy Vluggen wrote:

the guidelines from Microsoft

So, ummm... explain why Hashtable and DataTable don't agree. :suss:

[PIEBALDconsult]

For a (local) variable or a private field I use the former; otherwise "FileName". Camel case is only for use with Hungarian; and Hungarian is to be avoided. X|

[Lost User]

I'm not an employee, and I didn't claim it was consistent. It is however, always a good starting place for ideas, and a good place to end discussions.

Bastard Programmer from Hell :suss:

[Ravi Bhavnani]

VS' Code Analysis' built-in dictionary checks your identifiers for spelling, grammatical case and other naming conventions of the .NET Framework guidelines.  It's a great a way to gets started, and it's easy to modify/override spellings and naming conventions where necessary. /ravi

My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

[V 0]

variables: filename Properties, classes, methods... : FileName I hate constructs like sFileName or bMyBool to also indicate the type and also gVariable or _variable to indicate global or class variables, but that might be personal. ;)

V.

[Keith Barrow]

I personally prefer filename just as other people have stated, it is easy to read. Arguably it is becoming part of the language as a single word, I tend to think of filename as a more specific concept than name of a file that the version with the space implies. As an aside some dictionaries seem to agree .http://dictionary.reference.com/browse/filename[^]. FXCop disagrees and insists on fileName (see this blog post/[^]), and consistency are important. I'd rather agree with the framework and I assume MS uses FXCop's default rules .I can't find an example of fileName, but I'm 75% sure I've seen it somewhere... As a second point filename looks odd set aside filePath. So the answer is for consistancy go for fileName, but filename isn't so bad that you shouldn't use it if you find it easier to read, the important thing is to stick to one version in your code.

Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^]

[SilimSayo]

That's because one is a republican and the other, a democrat.

[SilimSayo]

I saw a variable declared as longAss. Ass was short for assignment no.

[Lost User]

That'd be a bigAss in Sql Server types :-D

Bastard Programmer from Hell :suss:

[SilimSayo]

:laugh:

[Abhinav S]

http://msdn.microsoft.com/en-us/library/xzf533w0%28v=vs.71%29.aspx[^] is a good guideline that you can always follow.

[AmitGajjar]

Hi, you can use StyleCop for coding convention. there are some rules for naming in it. thanks -Amit.

[Subin Mavunkal]

There are so many criterias.If it is a public property , make it "FileName".If it is a private member make it "_fileName" n for local variable make it "fileName".There are naming standards of c#.Go and read it.Or else install SCA for VS and make all naming warnings as errors.It will give u a good idea. :)

[Kevin McFarlane]

The link Eddy refers to is out of date (though probably still applies). The latest is here. http://msdn.microsoft.com/en-us/library/ms229042.aspx[^]

Kevin