How handle need for System.aspx form?

[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

[Alexey Smirnov]

On May 3, 6:35 am, "Ronald S. Cook" <[e-mail]:

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

Naming Guidelines by Microsoft
http://msdn2.microsoft.com/en-us/lib...w0(VS.71).aspx

[Ronald S. Cook]

I've been through that and it doesn't answer my question (so far as I can
tell).
"Alexey Smirnov" <al************@gmail.comwrote in message
news:11**********************@y5g2000hsa.googlegro ups.com...

On May 3, 6:35 am, "Ronald S. Cook" <[e-mail]:

>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

Naming Guidelines by Microsoft
http://msdn2.microsoft.com/en-us/lib...w0(VS.71).aspx

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

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

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Ronald S. Cook" wrote:

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

[Ronald S. Cook]

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.

"Peter Bromberg [C# MVP]" <pb*******@yahoo.yabbadabbadoo.comwrote in
message news:90**********************************@microsof t.com...

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

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Ronald S. Cook" wrote:

>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

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

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

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Ronald S. Cook" wrote:

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.

"Peter Bromberg [C# MVP]" <pb*******@yahoo.yabbadabbadoo.comwrote in
message news:90**********************************@microsof t.com...

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

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Ronald S. Cook" wrote:

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

[Ronald S. Cook]

That's my sickness :)
"Peter Bromberg [C# MVP]" <pb*******@yahoo.yabbadabbadoo.comwrote in
message news:F6**********************************@microsof t.com...

>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

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Ronald S. Cook" wrote:

>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.

"Peter Bromberg [C# MVP]" <pb*******@yahoo.yabbadabbadoo.comwrote in
message news:90**********************************@microsof t.com...

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

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Ronald S. Cook" wrote:

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