Re:A todo list for new ASP.NET Core projects
by hudo on Thursday February 08, 2018 @11:24AM
(#16333253)
Configuration can come from different sources, it can be reloaded, it can be lazy-loaded, there are so many different reasons why config is more like service and not a static variable.
It has to be injected.
Maybe you're using it in a way static access makes sense, but when you're designing generic Configuration solution, its whole another set of problems, requirements and constraints.
[ Parent
| on HN ]
Re:A todo list for new ASP.NET Core projects
by mattmanser on Friday February 09, 2018 @10:34AM
(#16340885)
No it's not. We've had app config for the last 20 years. When you need mutable config put it in the db.
There is a case for a mutable config, but it should be a separate class, and still wouldn't need to be a service.