命名空间和类名指南
当涉及 utils 和其他帮助类时，我在正确命名我的类和服务时遇到问题。
您将如何构建以下内容：
EventService.cs
EventServiceUtils.cs
EventServiceValidators.cs
EventServiceCoordinator.cs
等等...
我有多个服务与上述服务具有相同的需求。 一种想法是将所有这些分离到一个合适的命名空间中，使其看起来像这样：
Services.EventService.EventService.cs //(the actual service)
Services.EventService.Validators.DateValidator.cs
Services.EventService.Validators.ParticipantValidator.cs
Services.EventService.Coordinators.ParticipantCoordinator.cs
Services.EventService.ExtensionMethods.Extensions.cs
等等。每个命名空间当然都是一个单独的文件夹。 但这感觉并不是 100%，因为其他服务中可能有更多的 DateValidator，这很容易导致不需要的引用。
而且 Services.EventService.EventService.cs 在命名空间中包含类名，这也不好。您可以使用 Services.Event.EventService.cs，但当然已经有一个具有该名称的实体。
这就是领域模型。
Im having problems naming my classes and services correctly when utils and other help classes are involved.
How would you structure the following:
EventService.cs
EventServiceUtils.cs
EventServiceValidators.cs
EventServiceCoordinator.cs
etc...
I have multiple services with the same needs as the above service.
One thought is to separate all of this into a suitable namespace, making it look something like this:
Services.EventService.EventService.cs //(the actual service)
Services.EventService.Validators.DateValidator.cs
Services.EventService.Validators.ParticipantValidator.cs
Services.EventService.Coordinators.ParticipantCoordinator.cs
Services.EventService.ExtensionMethods.Extensions.cs
and so on. Every namespace is of course a separate folder.
But this doesnt feel 100%, since there are probably more DateValidators in the other services, which can easily lead to an unwanted reference.
And also the Services.EventService.EventService.cs includes the class name in the namespace, which is no good either. You could use Services.Event.EventService.cs, but there is of course already an entity with that name.
This is the domain model.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
要点：
可以在此处找到 Microsoft 指南：框架设计指南
Points:
Microsoft guidelines can be found here: Framework Design Guidelines
您可以将在多个服务中使用的验证器（和其他类）放置在名为例如的单独的命名空间中。通用验证器。
您可以更改
EventService.cs的名称，而不是更改命名空间的名称 - 可能是Main.cs或Default.cs？我假设您的服务在接口中有一个合同，因此这将指示服务合同的主要/默认实现。
You can put validators (and other classes) that are used in more than one service in seperate namespace named eg. CommonValidators.
You can change name of
EventService.csinstead of changing name of the namespace - maybeMain.csorDefault.cs?I am supposing that your service has a contract in interface so this would indicate main/default implementation of service contract.