blocks|key|4090163|text|我使用进入该名称空间的所有内容的公共描述符来命名我的名称空间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4090164|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

i name my namespaces with the common descriptor of all the things that go into that namespace.

blocks|key|880329|text|让类的名称与命名空间相同不是一个好主意--在我看来，这使得在某些情况下引用正确的东西变得相当棘手。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|880330|我通常将项目(和命名空间)命名为适当的名称，然后在适当的位置使用"EntryPoint“或"Program”作为入口点。在您的示例中，我可能会将这个类称为"KeepAliveService“。|880331|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Having the name of a class being the same as the namespace is a bad idea - it makes it quite tricky to refer to the right thing in some cases, in my opinion.

I usually call the project (and namespace) an appropriate name and then have "EntryPoint" or "Program" for the entry point where appropriate. In your example, I'd probably call the class "KeepAliveService".

blocks|key|22995|text|我们有一个简单的方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|22996|++CompanyName.ProductName|code-block|syntax|javascript|22997|然后是应用层，例如|22998|++CompanyName.ProductName.Data
++CompanyName.ProductName.Web|22999|等。|23000|并且在按模块和/或功能划分的内部，通常对应于文件夹|23001|++CompanyName.ProductName.Web.Shop
++CompanyName.ProductName.Web.Newsletter|23002|23003|顺便说一句:你可以在这里找到类似问题的答案：|23004|23005|.NET+namespaces|unordered-list-item|offset|length|23006|Should+the+folders+in+a+solution+match+the+namespace?|23007|23008|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/55692/net-namespaces|1|https://stackoverflow.com/questions/4664/should-the-folders-in-a-solution-match-the-namespace^0|0|0|0|0|0|0|0|0|0|0|0|F|0|0|0|1H|1|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1E|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1F|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1G|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1H|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1I|8|@]|9|@]|A|$E|F]]|$1|Q|3|L|5|6|7|1J|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1K|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|1M|8|@]|9|@$X|1N|Y|1O|1|1P]]|A|$]]|$1|Z|3|10|5|W|7|1Q|8|@]|9|@$X|1R|Y|1S|1|1T]]|A|$]]|$1|11|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]|1A|$5|15|16|17|A|$18|1B]]]]

We have this simple scheme:

<pre><code> CompanyName.ProductName
</code></pre>

Then the application layer, e.g.

<pre><code> CompanyName.ProductName.Data
 CompanyName.ProductName.Web
</code></pre>

etc.

And inside divided per module and/or functionality, which normally correspond to folders

<pre><code> CompanyName.ProductName.Web.Shop
 CompanyName.ProductName.Web.Newsletter
</code></pre>

etc.

BTW: You can find answers to similar questions here:

<ul>
<li><a href="https://stackoverflow.com/questions/55692/net-namespaces">.NET namespaces</a></li>
<li><a href="https://stackoverflow.com/questions/4664/should-the-folders-in-a-solution-match-the-namespace">Should the folders in a solution match the namespace?</a></li>
</ul>

blocks|key|875143|text|CompanyName.ProductName.AreaOfSystem.SubAreaOfSystem|type|unstyled|depth|inlineStyleRanges|entityRanges|data|875144|永远不要将它们称为类的同名。|875145|我们的领域包括：|875146|875147|Services|unordered-list-item|875148|Smartcard|875149|UI|875150|875151|子区域的使用率很低，但在相关情况下：|875152|875153|Smartcard.Mifare|875154|Smartcard.DESFire|875155|875156|我们的并不对应于文件夹，因为在逻辑上可能不是这样。为了简化解决方案资源管理器的导航，我们可能会在文件夹中划分某些部分，但这并不一定意味着命名空间应该遵循文件夹结构。尤其是在文件夹中只有几个文件的情况下(只有几个类型的命名空间通常是愚蠢的)。|875157|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|I|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|I|7|16|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|R|3|S|5|I|7|1A|8|@]|9|@]|A|$]]|$1|T|3|U|5|I|7|1B|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1D|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|Z|$]]

CompanyName.ProductName.AreaOfSystem.SubAreaOfSystem

Never call them the same name as a class.

Our areas include things like:

<ul>
<li>Services</li>
<li>Smartcard</li>
<li>UI</li>
</ul>

Sub-areas are used sparingly but when relevant:

<ul>
<li>Smartcard.Mifare</li>
<li>Smartcard.DESFire</li>
</ul>

Ours don't correspond to folders because logically that may not be the case. To ease solution explorer navigation we might section off certain bits in folders but that doesn't necessarily mean the namespaces should follow the folder structure. Especially if there are only a few files in the folder (a namespace with few types is usually silly).

blocks|key|4090345|text|我喜欢java包的方式:+com.stackoverflow.Data+(或者你公司的主域名是什么)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4090346|这样你的命名空间就不会模棱两可了。|4090347|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I like the java package way: com.stackoverflow.Data (or whatwever the primary domain name of your company may be). 
That way your namespaces won't be ambiguous.

blocks|key|3245116|text|我们坚持老一套|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3245117|uk.co.company.system.layer|3245118|当我们使用大量的MS+Server产品时，我们将冲突减少到最低限度，这有助于概念上的分离。|3245119|例如：|3245120|uk.co.acme.biztalk.bizutils。|3245121|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

we stick to the old

uk.co.company.system.layer

scheme that way we keep collisions down to a miniumum as we use a lot of MS Server products and it helps conceptual seperations.

eg.

uk.co.acme.biztalk.bizutils.

In the past I've always gone and called my namespace for a particular project the same as the project (and principle class) e.g.:

<pre><code>namespace KeepAlive
{
 public partial class KeepAlive : ServiceBase
 {...
</code></pre>

Then from other projects whenever i've called that class its always been:

<pre><code>KeepAlive.KeepAlive()...
</code></pre>

I'm now beginning to think that this might not be such a good idea, but I'm sort of stumped what to actually call my namespace. What do other people do? Do you just have one namespace for all your projects?

What is best thing to call your namespace in .Net

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在过去，我总是使用与项目(和主要类)相同的名称空间来命名特定项目，例如：namespace KeepAlive{    public partial class KeepAlive : ServiceBase    {...然后在其他项目中，每当我调用那个类时，它总是：KeepAlive.KeepAlive()...我...

问在.Net中命名空间最合适的名称是什么
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在.Net中命名空间最合适的名称是什么EN