«

Hello,

Numerous people have kindly commented on my use of the Hungarian style
naming convention, which I am appreciative of. In trying to move away from
this naming style, I have run into some difficulty. For example, I have a
application that has something like the following:

Text Box: txtLastName
Label: lblLastName
HiddenValue: hdnLastName

In terms of best practice, how should I name these three objects? Any help
with this would be appreciated.

Thanks, sck10

"sck10" <> wrote in message
news:OShK%...

> In trying to move away from this naming style,

Why are you trying to do that...?

> Text Box: txtLastName
> Label: lblLastName
> HiddenValue: hdnLastName

Looks fine to me - if it ain't broke, don't fix it...

Looks fine to me, I am also using the same "camel" style if the declaration
are private. Public and protected names usually start with a capital.

--
Eliyahu Goldin,
Software Developer & Consultant
Microsoft MVP [ASP.NET]


"sck10" <> wrote in message
news:OShK%...
> Hello,
>
> Numerous people have kindly commented on my use of the Hungarian style
> naming convention, which I am appreciative of. In trying to move away
> from this naming style, I have run into some difficulty. For example, I
> have a application that has something like the following:
>
> Text Box: txtLastName
> Label: lblLastName
> HiddenValue: hdnLastName
>
> In terms of best practice, how should I name these three objects? Any
> help with this would be appreciated.
>
> Thanks, sck10
>

Well, this all started when MSFT released a document stating that Hungarian
style programming is discouraged. I don't see why for so many years this was
quite fine; but now all of the sudden with .NET it is discouraged. You can
use variation of styles. They recommend stuff like:

lastNameTextBox
LastName
lastName

but to tell you the truth, this is all hogwash. If you find a style that
your are comfortable with, stick with it. Or, if you company has a set
standard use it. Otherwise, ignore what others are saying. Is is
non-productive.


"sck10" <> wrote in message
news:OShK#...
> Hello,
>
> Numerous people have kindly commented on my use of the Hungarian style
> naming convention, which I am appreciative of. In trying to move away
> from this naming style, I have run into some difficulty. For example, I
> have a application that has something like the following:
>
> Text Box: txtLastName
> Label: lblLastName
> HiddenValue: hdnLastName
>
> In terms of best practice, how should I name these three objects? Any
> help with this would be appreciated.
>
> Thanks, sck10
>

"tdavisjr" <> wrote in message
news:...

> Well, this all started when MSFT released a document stating that
> Hungarian style programming is discouraged. I don't see why for so many
> years this was quite fine; but now all of the sudden with .NET it is
> discouraged. You can use variation of styles. They recommend stuff like:
>
> lastNameTextBox
> LastName
> lastName
>
> but to tell you the truth, this is all hogwash. If you find a style that
> your are comfortable with, stick with it. Or, if you company has a set
> standard use it. Otherwise, ignore what others are saying. Is is
> non-productive.

I couldn't agree more!

Hi Steve,

I think tdavisjr has given you a quite good answer:

===============
If you find a style that your are comfortable with, stick with it. Or, if
you company has a set standard use it. Otherwise, ignore what others are
saying. Is is non-productive.
==============

Just coding as you like

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.

All,

Thanks for the feedback...

sck10


"Steven Cheng[MSFT]" <> wrote in message
news:...
> Hi Steve,
>
> I think tdavisjr has given you a quite good answer:
>
> ===============
> If you find a style that your are comfortable with, stick with it. Or, if
> you company has a set standard use it. Otherwise, ignore what others are
> saying. Is is non-productive.
> ==============
>
> Just coding as you like
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>