使用服务集合来配置设置或在.Net Core中添加单例之间有什么区别？

Question

On startup of our asp net core applications we read a whole bunch of configuration from our appsettings.json and map it to a concrete type that we inject in our service layer.

Consider the two examples below :

A : services.AddSingleton(Configuration.GetSection("Auth0").Get<Auth0Settings>());

B : services.Configure<Auth0Settings>(Configuration);

I know using option AI can simply inject the concrete type into my constructor and use it whereas with option BI am required to use the Options Pattern

Im unsure what benefits option B provides over option A and why I would use it.

Answer 1

In the end both approaches give the same result and you cann access an instance of Auth0Settings via DI in eg your controllers.

For me there are two arguments in favor of the Options-Pattern .

1. Expressivness - you make a clear destinction about application logic (services) and configuration (options). This make your code better to read and your intent easer to understand.

2. Flexibility - the Options-Pattern provides additional features (like validation and post-processing)

Although you might not need the additional features the first argument is still on the plate.