Naming conventions?

[Allan Ebdrup]

Does anyone have some good pointers to good naming conventions preferrably
by MS.

Another developer and I had a discussion on the naming of a public property
that contains a collection of variables.
He wants to call it "Parameter" like when you name tables in SQL, I want to
call it "Parameters" so you can see that it contains several values. What is
the correct naming in OO, and do you have a pointer to a document that
describes these naming conventions?

Kind Regards,
Allan Ebdrup

[Rakesh Rajan]

Hi,

Check out:
http://msdn.microsoft.com/library/de...guidelines.asp

--
HTH,
Rakesh Rajan
MVP, MCSD
http://www.msmvps.com/rakeshrajan/

"Allan Ebdrup" wrote:

Does anyone have some good pointers to good naming conventions preferrably
by MS.

Another developer and I had a discussion on the naming of a public property
that contains a collection of variables.
He wants to call it "Parameter" like when you name tables in SQL, I want to
call it "Parameters" so you can see that it contains several values. What is
the correct naming in OO, and do you have a pointer to a document that
describes these naming conventions?

Kind Regards,
Allan Ebdrup

[Allan Ebdrup]

"Rakesh Rajan" <rakeshrajan {at} mvps {dot} org> wrote in message
news:C8**********************************@microsof t.com...

Check out:
http://msdn.microsoft.com/library/de...guidelines.asp

Thanks Rakesh, however I can't find anything clearing up the problem I
describe in the above.

Kind Regards,
Allan Ebdrup

[Carlos J. Quintero [.NET MVP]]

Hi Allan,

In OOP "Parameters" is more suitable than "Parameter" for a property of the
type ArrayList, Collection, etc. The best argument to convince your fellow
is to use the Object Browser and take a look at the Microsoft .NET Framework
libraries. You will notice that while classes are named like
"ListView.ColumnHeaderCollection", the property is named ListView.Columns.
--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

"Allan Ebdrup" <co****@ofir.com> escribió en el mensaje
news:%2****************@TK2MSFTNGP09.phx.gbl...

Does anyone have some good pointers to good naming conventions preferrably
by MS.

Another developer and I had a discussion on the naming of a public
property that contains a collection of variables.
He wants to call it "Parameter" like when you name tables in SQL, I want
to call it "Parameters" so you can see that it contains several values.
What is the correct naming in OO, and do you have a pointer to a document
that describes these naming conventions?

Kind Regards,
Allan Ebdrup

[Michael S]

"Allan Ebdrup" <co****@ofir.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

Does anyone have some good pointers to good naming conventions preferrably
by MS.

Another developer and I had a discussion on the naming of a public
property that contains a collection of variables.
He wants to call it "Parameter" like when you name tables in SQL, I want
to call it "Parameters" so you can see that it contains several values.
What is the correct naming in OO, and do you have a pointer to a document
that describes these naming conventions?

Kind Regards,
Allan Ebdrup

There is no question about it. You should use 'Parameters'.
Look at the overall naming convention in .NET framework. Examples:

Request.QueryString.Keys[0];
myDataset.Tables[0].Rows[0];

- Michael S

[Allan Ebdrup]

"Michael S" <a@b.c> wrote in message
news:uq*************@TK2MSFTNGP12.phx.gbl...

There is no question about it. You should use 'Parameters'.
Look at the overall naming convention in .NET framework. Examples:

Request.QueryString.Keys[0];
myDataset.Tables[0].Rows[0];

I will precent the evidence and hopefully convince him that "Parameters" is
the correct choice. Thanks for your feedback.