Naming Conventions

[mac]

Brand new to C# and I like it so far. I don't want to start a flame war
over naming conventions.

I do want to find a comprehensive convention, learn it, and start using it
right from the start. Does anyone have any suggestions for where I could
find a *concise* document that spells out a convention.

I want:

1. A widely used convention.
2. One that covers all the different variables and objects I wll have to
name
3. A spec that avoids lots of justification, and just gives the facts.

Coming from a database background, I generally don't like CamelCasing, but
it that is what the bulk of the coders are doing, I'll do it too.

Thanks,

Mac

[Galcho[MCSD.NET]]

see here: Designing .NET Class Libraries: Naming Conventions
http://msdn.microsoft.com/netframewo...ngconventions/

MS Created very good documents about this
I hope this helps
Galin Iliev[MCSD.NET]
www.galcho.com

mac wrote:

Brand new to C# and I like it so far. I don't want to start a flame war
over naming conventions.

I do want to find a comprehensive convention, learn it, and start using it
right from the start. Does anyone have any suggestions for where I could
find a *concise* document that spells out a convention.

I want:

1. A widely used convention.
2. One that covers all the different variables and objects I wll have to
name
3. A spec that avoids lots of justification, and just gives the facts.

Coming from a database background, I generally don't like CamelCasing, but
it that is what the bulk of the coders are doing, I'll do it too.

Thanks,

Mac

[mac]

Galcho,

Thanks for the tip, this is what I wanted.

Thanks,

Mac

"mac" <ma*@mac.com> wrote in message news:tA4mg.547$Nv.468@fed1read10...

Brand new to C# and I like it so far. I don't want to start a flame war
over naming conventions.

I do want to find a comprehensive convention, learn it, and start using it
right from the start. Does anyone have any suggestions for where I could
find a *concise* document that spells out a convention.

I want:

1. A widely used convention.
2. One that covers all the different variables and objects I wll have to
name
3. A spec that avoids lots of justification, and just gives the facts.

Coming from a database background, I generally don't like CamelCasing, but
it that is what the bulk of the coders are doing, I'll do it too.

Thanks,

Mac