R
Ronald S. Cook
An ongoing philosophical argument, I would like your opinions. With the
release of .NET, Microsoft spoke of moving away from the notation as a best
practice. I'm a believer for a few reasons:
1) Consistency throughout and knowing which objects are yours
(clsEmployee, tblEmployee, frmEmployee, etc).
2) Not having to name an employee form EmployeeForm.aspx because the
mane is already taken by your class named Employee.cs
3) We once had a major entity "System" in our model. Because it's
reserved name, would have to alias somehow anyway.
4) I just created a form "Login.aspx" in an ASP.NET 2.0 app. That's now
a conflict with the new "Login" control.
Does anyone disagree with using Hungarian notation? If so, I'd be
interested to hear specific bullets of why you don't like it (and also what
you would do to avoid naming conflicts).
Thanks,
Ron
release of .NET, Microsoft spoke of moving away from the notation as a best
practice. I'm a believer for a few reasons:
1) Consistency throughout and knowing which objects are yours
(clsEmployee, tblEmployee, frmEmployee, etc).
2) Not having to name an employee form EmployeeForm.aspx because the
mane is already taken by your class named Employee.cs
3) We once had a major entity "System" in our model. Because it's
reserved name, would have to alias somehow anyway.
4) I just created a form "Login.aspx" in an ASP.NET 2.0 app. That's now
a conflict with the new "Login" control.
Does anyone disagree with using Hungarian notation? If so, I'd be
interested to hear specific bullets of why you don't like it (and also what
you would do to avoid naming conflicts).
Thanks,
Ron