naming conventions forced by VS.NET?

[Pieter]

Hi,

I thouht that I read somewhere that Visual Studio .NET 2005 is able to force
naming conventions for controls etc., but I can't find it anymore :-/ did I
dream this or is this real? :-) If it's real: how can I do this?

Thanks a lot in advance,

Pieter

[William Sullivan]

RE: naming conventions forced by VS.NET?

I don't know how you'd even do that. Are you talking about casing, or
default names? You might be mixing this up with Code Analysis. Code
Analysis will check your code against several standard programming practices,
including variable name casings...

"Pieter" wrote:

Hi,
>
I thouht that I read somewhere that Visual Studio .NET 2005 is able to force
naming conventions for controls etc., but I can't find it anymore :-/ did I
dream this or is this real? :-) If it's real: how can I do this?
>
Thanks a lot in advance,
>
Pieter
>
>
>

[Pieter]

Re: naming conventions forced by VS.NET?

I am talking about casing, for isntance: every TextBox must have the prefix
"txt" etc...

"William Sullivan" <WilliamSulliva n@discussions.m icrosoft.comwro te in
message news:870F40F2-40B8-4D77-AF01-8656FAD0A37D@mi crosoft.com...

>I don't know how you'd even do that. Are you talking about casing, or
default names? You might be mixing this up with Code Analysis. Code
Analysis will check your code against several standard programming
practices,
including variable name casings...

[Phill W.]

Re: naming conventions forced by VS.NET?

Pieter wrote:

I thouht that I read somewhere that Visual Studio .NET 2005 is able to force
naming conventions for controls etc., but I can't find it anymore

This is probably part of the really, /really/ expensive version of V.S.

For mere mortals, requisition a baseball bat with which to "encourage"
your Developers.

Regards,
Phill W.

[Pieter]

Re: naming conventions forced by VS.NET?

I use a whip :-) But it would be nice if some kind of applicaton could tell
me how many thimes I have to hit them, instead of counting the errors myself
:-)

Especially if I could write an interface for it for my USB-whip, so i don't
have to hit them anymore myselves :-)

"Phill W." <p-.-a-.-w-a-r-d@o-p-e-n-.-a-c-.-u-kwrote in message
news:ejup66$39o $1@south.jnrs.j a.net...

For mere mortals, requisition a baseball bat with which to "encourage"
your Developers.

[Tim Patrick]

Re: naming conventions forced by VS.NET?

There is no enforcement of control or member names in Visual Basic; you can
give them any names you want. The standards you referenced--such as prefixing
TextBox controls with "txt"--are a mixture of Visual Basic tradition and
an older naming system called "Hungarian" (seriously!). They are no longer
recommended for Visual Basic development.

In the online help for Visual Studio, look up "naming guidelines [.NET Framework]"
in the index. There you will find the new recommendations . I also talk about
naming standards in my book _The Visual Basic .NET Style Guide_. I think
you can buy a used copy for about one dollar on Amazon.com.

-----
Tim Patrick - www.timaki.com
Start-to-Finish Visual Basic 2005

I am talking about casing, for isntance: every TextBox must have the
prefix "txt" etc...
>
"William Sullivan" <WilliamSulliva n@discussions.m icrosoft.comwro te
in message news:870F40F2-40B8-4D77-AF01-8656FAD0A37D@mi crosoft.com...
>

>I don't know how you'd even do that. Are you talking about casing,
>or
>default names? You might be mixing this up with Code Analysis. Code
>Analysis will check your code against several standard programming
>practices,
>including variable name casings...

[Pieter]

Re: naming conventions forced by VS.NET?

I know the hungarian notation isn't 'a standard'anymor e, but in my opinion
it still has the most benefits, so that's why I want it to have it
everywhere :-)

[Carlos J. Quintero [VB MVP]]

Re: naming conventions forced by VS.NET?

My MZ-Tools add-in (below) has two features that can help:

- Control Default Properties: you can define prefixes for the Name property
of each control and every time you drop a control it gets that prefix.

- Review Control Default Properties: you can find the occurrences of
controls that don't follow your standard and you can prevent the build if
you configure so.

There are many other features and reviews and you can even build your own
custom review with the MZ-Tools SDK.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:

http://www.mztools.com

"Pieter" <pieterNOSPAMco ucke@hotmail.co mescribió en el mensaje
news:eBGVW%23ID HHA.3536@TK2MSF TNGP02.phx.gbl. ..

Hi,
>
I thouht that I read somewhere that Visual Studio .NET 2005 is able to
force naming conventions for controls etc., but I can't find it anymore
:-/ did I dream this or is this real? :-) If it's real: how can I do this?
>
Thanks a lot in advance,
>
Pieter
>

[Pieter]

Re: naming conventions forced by VS.NET?

Thanks, it looks nice. I didn't yet download the demo, but I sure will next
week.
Just some questions:
- During how many time can I try the demo?
- How exactly can I put my own coding-standards (the prefixes of every type
control) in it? Do you have a sample of it? It would be nice if I could
import them from Excle or something like that? And can this be done with the
demo?

Thansk a lot in advance,

Pieter

"Carlos J. Quintero [VB MVP]" <nospam@nospam. comwrote in message
news:u7%23PBbiD HHA.348@TK2MSFT NGP06.phx.gbl.. .

My MZ-Tools add-in (below) has two features that can help:
>
- Control Default Properties: you can define prefixes for the Name
property of each control and every time you drop a control it gets that
prefix.
>
- Review Control Default Properties: you can find the occurrences of
controls that don't follow your standard and you can prevent the build if
you configure so.
>
There are many other features and reviews and you can even build your own
custom review with the MZ-Tools SDK.
>
--
>
Best regards,
>
Carlos J. Quintero
>
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com

[Carlos J. Quintero [VB MVP]]

Re: naming conventions forced by VS.NET?

Hi Pieter,

You can use the demo version during 30 days. To use the control prefixes you
do the following:

- Go to the MZ-Tools, Options, Corporate Options window
- Select the Control Default Properties section
- In the first combobox, select the referenced System.Windows. Forms assembly
(you need to have a Windows Forms project open)
- For each Component, select the "Name (prefix)" property and enter a value,
for example "txt" for the TextBox control, etc.

Once you have done that, the features "Prompt Name and Text Properties for
New Control", the "Apply Default Properties", "Review Control Default
Properties", etc. will honor it.

Let me know if you need further assistance when evaluating it.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:

http://www.mztools.com

"Pieter" <pieterNOSPAMco ucke@hotmail.co mescribió en el mensaje
news:OxULuKvDHH A.3836@TK2MSFTN GP02.phx.gbl...

Thanks, it looks nice. I didn't yet download the demo, but I sure will
next week.
Just some questions:
- During how many time can I try the demo?
- How exactly can I put my own coding-standards (the prefixes of every
type control) in it? Do you have a sample of it? It would be nice if I
could import them from Excle or something like that? And can this be done
with the demo?
>
Thansk a lot in advance,
>
Pieter