IMHO, for private or internal procedures, class or procedure variables, etc.
you can use whatever naming convention you like, but for code elements
(classes, procedures, parameters) which are exposed outside your assembly,
you should follow the MS naming conventions.
--
Carlos J. Quintero
MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com
"Cor Ligthert" <no************@planet.nl> escribió en el mensaje
news:eW**************@tk2msftngp13.phx.gbl...
Herfried,
Should or would?
Cor
"Herfried K. Wagner [MVP]" <hi***************@gmx.at>
"rastaman" <ge*************@hotmail.com> schrieb: I wonder if I can use the same naming conventions as for VB6 ? If so,
what
about the names for the new objects in .NET.
Everybody can use his/her own naming convention. Nevertheless, class
library developers should follow conventions published by Microsoft:
Naming guidelines and code conventions
<URL:http://dotnet.mvps.org/dotnet/faqs/?id=namingconventions&lang=en>
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>