你将如何处理所需的“系统”？应用程序中的类/表/表单？ [英] How would you handle needed "System" class/table/form in application?
问题描述
我只是好奇你将如何处理这个问题。在有线电视行业，Comcast
被称为MSO。 （多系统运营商）意味着他们拥有许多
电缆系统。因此，必须设计一个解决方案以适应
系统。作为一个实体。这意味着数据库中的一个表名为System，一个
类系统，一个Web表单系统等。
由于系统是这样一个保留字，如何我们应该这样做吗？重命名
" CableSystem"会因为不一致/需要什么而导致错误（应该因为与开发工具发生冲突而需要改变我们的业务术语）。
对于班级来说，它可能是命名为系统并且只需将命名空间封装在名称为Classes的名称为
的名称中。但是对于Web表单，虽然它可以命名为
System.aspx，但你不能只是在它周围包装命名空间。
匈牙利表示法是"列"这些天所以我正在寻找一个好的
标准化和一致的方法来处理所有可能发生冲突的名字。
谢谢，
Ron
I''m just curious how you would handle this. In the cable industry, Comcast
is referred to as an "MSO" (multiple systems operator) meaning they own many
cable systems. Therefore a solution must be architected to accommodate
"System" as an entity. This means a table in the database named System, a
class System, a web form System, etc.
Since System is such a reserved word, how should we do this? To rename it
"CableSystem" would bug as isn''t consistent/what is desired (should have to
change our business terminology because conflicts with development tool).
For the class, it could be named "System" and just wrapper a namespace
around it named "Classes". But for the web form, while it could be named
System.aspx, you can''t just wrap a namespace around it.
Hungarian notation is "out" these days so I''m looking for a good
standardized and consistent approach for all such names that might conflict.
Thanks,
Ron
推荐答案
Ronald S. Cook< rc *** @ westinis.comwrote：
Ronald S. Cook <rc***@westinis.comwrote:
我很好奇你将如何处理这个问题。在有线电视行业，Comcast
被称为MSO。 （多系统运营商）意味着他们拥有许多
电缆系统。因此，必须设计一个解决方案以适应
系统。作为一个实体。这意味着数据库中的一个表名为System，一个
类系统，一个Web表单系统等。
由于系统是这样一个保留字，如何我们应该这样做吗？重命名
" CableSystem"会因为不一致/需要什么而导致错误（应该因为与开发工具发生冲突而需要改变我们的业务术语）。
对于班级来说，它可能是命名为系统并且只需将命名空间封装在名称为Classes的名称为
的名称中。但对于Web表单，虽然它可以命名为
System.aspx，但你不能只是在它周围包装命名空间。
I''m just curious how you would handle this. In the cable industry, Comcast
is referred to as an "MSO" (multiple systems operator) meaning they own many
cable systems. Therefore a solution must be architected to accommodate
"System" as an entity. This means a table in the database named System, a
class System, a web form System, etc.
Since System is such a reserved word, how should we do this? To rename it
"CableSystem" would bug as isn''t consistent/what is desired (should have to
change our business terminology because conflicts with development tool).
For the class, it could be named "System" and just wrapper a namespace
around it named "Classes". But for the web form, while it could be named
System.aspx, you can''t just wrap a namespace around it.
系统不是一个保留字 - 它只是一个突出的命名空间。使用System作为
类的名称可能有点痛苦，但它应该是可行的。你有什么问题？
-
Jon Skeet - < sk *** @ pobox.com>
http://www.pobox.com/~skeet 博客： http://www.msmvps.com/jon.skeet
如果回复对于小组，请不要给我发邮件
System isn''t a reserved word - it''s just a prominent namespace. It''s
likely to be a bit of a pain working with System as the name of a
class, but it should be doable. What problems are you having?
--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
嗯，Web表单继承自System.Web ...所以即使我把它包装成
命名空间，不会飞。
" Jon Skeet [C＃MVP]" < sk *** @ pobox.com写了留言
新闻：MP ******************** @ msnews.microsoft.com。 ......
Well, the web form inherits from System.Web... so even if I wrap it in a
namespace, that doesn''t fly.
"Jon Skeet [C# MVP]" <sk***@pobox.comwrote in message
news:MP********************@msnews.microsoft.com.. .
Ronald S. Cook< rc *** @ westinis.comwrote：
Ronald S. Cook <rc***@westinis.comwrote:
> I 我只是好奇你将如何处理这个问题。在有线电视行业，Comcast
被称为MSO。 （多系统操作员）意味着他们拥有许多
电缆系统。因此，必须设计解决方案以适应系统。作为一个实体。这意味着数据库中的一个表名为System，
一个类系统，一个Web表单系统等。
由于System是一个保留字，我们该怎么做呢？重命名
它
CableSystem会因为与开发工具发生冲突而不一致/需要什么（应该改变我们的业务术语）。
对于这个类，它可以被命名为System ;并且只是在它周围包装一个名为Classes的命名空间。但是对于Web表单，虽然它可以命名为System.aspx，但你不能只是在它周围包装命名空间。
>I''m just curious how you would handle this. In the cable industry,
Comcast
is referred to as an "MSO" (multiple systems operator) meaning they own
many
cable systems. Therefore a solution must be architected to accommodate
"System" as an entity. This means a table in the database named System,
a
class System, a web form System, etc.
Since System is such a reserved word, how should we do this? To rename
it
"CableSystem" would bug as isn''t consistent/what is desired (should have
to
change our business terminology because conflicts with development tool).
For the class, it could be named "System" and just wrapper a namespace
around it named "Classes". But for the web form, while it could be named
System.aspx, you can''t just wrap a namespace around it.
系统不是一个保守的词 - 它只是一个突出的命名空间。使用System作为
类的名称可能有点痛苦，但它应该是可行的。你有什么问题？
-
Jon Skeet - < sk *** @ pobox.com>
http://www.pobox.com/~skeet 博客： http://www.msmvps.com/jon.skeet
如果回复对于小组，请不要给我发邮件
System isn''t a reserved word - it''s just a prominent namespace. It''s
likely to be a bit of a pain working with System as the name of a
class, but it should be doable. What problems are you having?
--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
Ronald S. Cook< rc *** @ westinis.comwrote：
Ronald S. Cook <rc***@westinis.comwrote:
嗯，Web表单继承自System.Web ...所以即使我将它包装在
命名空间中，也不会飞。
Well, the web form inherits from System.Web... so even if I wrap it in a
namespace, that doesn''t fly.
如果没有它实际阻止你的地方的例子，很难
帮助更多，我''我很害怕。
-
Jon Skeet - < sk *** @ pobox.com>
http://www.pobox.com/~skeet 博客： http://www.msmvps.com/jon.skeet
如果回复群组，请不要给我发邮件
Without an example of where it''s actually stopping you, it''s hard to
help much more, I''m afraid.
--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
这篇关于你将如何处理所需的“系统”？应用程序中的类/表/表单？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
