在 C# 中哪里定义特定于服务的枚举？

发布于 2025-01-02 19:53:36 字数 1287 浏览 0 评论 0原文

假设我有一个接口 ICustomerService 并且该接口需要一个枚举，例如 ProcessingMode：

namespace MyServices {
    public enum ProcessingMode { Immediate, Normal, Slow }

    public interface ICustomerService {
        void Process(ProcessingMode mode);
    }
}

枚举不能在 C# 中的接口内部定义（但显然是在 VB 中？）。但是将其放在界面之外会使包含名称空间 MyServices 变得混乱。不好，因为其他接口可能还需要一个名为 ProcessingMode 的不同枚举。

那么有什么“最佳实践”来解决这个问题吗？

我可以看到一些选项，但对我来说似乎没有一个是完全正确的：

将接口和枚举都放在特定于服务的命名空间中：
```
命名空间 MyServices.CustomerService {
    公共枚举处理模式 { 立即、正常、慢速 }

    公共接口 ICustomerService {
        void Process(ProcessingMode 模式);
    }
}
```
虽然它可以工作并避免包含命名空间中的混乱，但它确实会导致命名空间扩散，并且我猜想服务实现可能会与命名空间发生冲突或重复它：MyNamespace.CustomerService.CustomerService。或者将服务实现放在哪里以及如何称呼它？

仅将枚举放入单独的命名空间（或静态类）中：

命名空间 MyServices {
    命名空间 CustomerServiceTypes {
        公共枚举处理模式 { 立即、正常、慢速 }
    }

    公共接口 ICustomerService {
        void Process(CustomerServiceTypes.ProcessingMode 模式);
    }
}

与选项 1 的问题相同，但还需要“在任何地方”限定枚举名称。

添加枚举名称前缀，例如CustomerServiceProcessingMode。避免名称空间扩散以及与服务实现发生名称冲突的风险，但会导致枚举名称过长且丑陋。

那么你会怎么做呢？

原文

Let's say I have an interface ICustomerService and this interface requires an enum, e.g. ProcessingMode:

namespace MyServices {
    public enum ProcessingMode { Immediate, Normal, Slow }

    public interface ICustomerService {
        void Process(ProcessingMode mode);
    }
}

The enum can't be defined inside the interface in C# (but apparently in VB?). But having it outside the interface clutters the containing namespace MyServices. Not good, since other interfaces might also require a different enum called ProcessingMode.

So are there any "best practices" how to solve this?

I can see a few options, but none of them seems quite right to me:

Put both the interface and the enum in a service-specific namespace:
```
namespace MyServices.CustomerService {
    public enum ProcessingMode { Immediate, Normal, Slow }

    public interface ICustomerService {
        void Process(ProcessingMode mode);
    }
}
```
While it works and avoids clutter in the containing namespace, it does cause namespace proliferation, and I guess a service implementation might clash with the namespace or duplicate it: MyNamespace.CustomerService.CustomerService. Or where would you put the service implementation and what would you call it?

Put just the enum in a separate namespace (or a static class):

namespace MyServices {
    namespace CustomerServiceTypes {
        public enum ProcessingMode { Immediate, Normal, Slow }
    }

    public interface ICustomerService {
        void Process(CustomerServiceTypes.ProcessingMode mode);
    }
}

Same problems as option 1 but also requires a enum name to be qualified "everywhere".

Prefix the enum name, e.g. CustomerServiceProcessingMode. Avoids namespace proliferation and risk of name clashes with service implementations, but causes long ugly enum names.

So how would you do it?

分享到QQ

分享到微博