How handle need for System.aspx form?

  • Thread starter Thread starter Ronald S. Cook
  • Start date Start date
R

Ronald S. Cook

I want to name a form "System", let's say. While I know I can name it
System.aspx and change the class name within to something like SystemForm, I
don't think that's a good practice.

public partial class SystemForm : System.Web.UI.Page

I tried wrapping it within a namespace "Forms" but that doesn't help.

Is there a recommendation that can be applied consistently (as a development
standard) across all forms whether they conflict with a .NET name or not?
Since Hungarian is supposedly on the way out, clsSystem is no longer a
"proper" option either.

Thanks,
Ron
 
I want to name a form "System", let's say. While I know I can name it
System.aspx and change the class name within to something like SystemForm, I
don't think that's a good practice.

public partial class SystemForm : System.Web.UI.Page

I tried wrapping it within a namespace "Forms" but that doesn't help.

Is there a recommendation that can be applied consistently (as a development
standard) across all forms whether they conflict with a .NET name or not?
Since Hungarian is supposedly on the way out, clsSystem is no longer a
"proper" option either.

Thanks,
Ron
Click to expand...

Naming Guidelines by Microsoft
http://msdn2.microsoft.com/en-us/library/xzf533w0(VS.71).aspx
 
I've been through that and it doesn't answer my question (so far as I can
tell).
 
Actually I think the naming guidelines are pretty clear in recommending *NOT*
to name classes / objects with names that confuse with existing namespaces or
classes.

Why do you "have to do this" - which will likely only cause readability and
maintainability issues down the road?
Peter
 
Just a pain that because of reserved words, System (the ideal name for an
entity) has to be prefixed or postfixed with a word to prevent conflict.
Although the world is pushing to move away from Hungarian, these kinds of
things ,make sense to keep it. Take for example a desired table "User".
Because is a SQL reserved word, have to bracket it every time is written or
use some other less desireable name. Just bugs me when the technical
environment dictates what things can and can't be named.
 
That's my sickness :)


Peter Bromberg said:
I understand. There are lots of things in the world that you can't change,
or
at least not easily. You can easily spend a lot of time harping on them
too.
Peter
Click to expand...
 
Back
Top