Naming Rules

[Adriaan Davel]

Hi, I'm looking for the (class / property / etc) naming rules in c#. I thought 'surely the language specification must have them' and 'surely Google can tell me', problem is I keep finding naming conventions etc etc. I need the RULES, e.g. You may not start a property name with a number. The stuff that makes the compiler break... I don't care about upper case vs lower case etc, those are conventions...

____________________________________________________________ Be brave little warrior, be VERY brave

[Bigdeak]

Hello, you may look for design patterns. There are not only the rule for class names, the design patterns are really good for common design stuff. For example: If you want to implement a undo/redo feature to you application, the Memento pattern ist the right. Here is a list of more design patterns: Design Patterns

[Adriaan Davel]

Hi, thanks for your reply but I am not looking for design patterns (I am familiar with a vast array of them already), I'm looking for a definitive list of rules for naming in c#

____________________________________________________________ Be brave little warrior, be VERY brave

[Pete OHanlon]

You might find the ECMA Spec for C# useful. It's available here[^].

I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be

My blog | My articles | MoXAML PowerToys | Onyx

[Lost User]

Another alternative is on MSDN[^] :)

I are Troll :suss:

[Bigdeak]

Ah, i thought design patterns would be ah good basis how to name classes at least. Sorry if my answer couldn't help you.

[Kythen]

See section 2.4.2 Identifiers of the CSharp Language Specification available from MSDN at http://msdn.microsoft.com/en-us/library/ms228593.aspx[^] Generally speaking, identifiers must start with a letter or underscore and can follow with almost any unicode character. If the identifier is a keyword, it must be prefixed with an '@' character.