
Does anybody do the .AddApplicationServices thing in real projects?
Ive been seeing this pattern for a while, in all kinds of sample architecture templates like this one here.
The pattern is instead of registering everything in program.cs, you extract it and have 10 places with 50 lines of registration code, instead of 1 place with 500 lines of registration code.
The same pattern you can do in a DbContext with OnModelCreating. You can either do it all in one file, or split it up.
In real projects I pretty much only see the all in one file approach. I think it makes more sense too, its more honest. Some classes are just big. If I have 100 tables, im gonna have 100 db sets and probably like 1000 lines of model configuration.
Do you find it annoying in real life projects? Or is it just fine? Do you think its better to split? Does it lead to philisophical discussions?