4 ms·
Sadly me and many others in large corporate environments. Not quite that bad but still pretty bad. My advice to people is to consolidate projects wherever poss
by flukus 5y ago
Sadly me and many others in large corporate environments. Not quite that bad but still pretty bad.
My advice to people is to consolidate projects wherever possible, although you wouldn't know it seeing some project layouts you can still have separate namespaces and folders inside projects. I think many do this in the hope it will help build times but it does the opposite, msbuild is the slow part and csc (the c# compiler) is lightning fast, so make it do the heavy lifting.
- tracker1 5y agoYeah, if your projects are so tightly coupled that you have to work on them in the same Solution, then you may as well Join them most of the time. Another bit, I would generally have the Interfaces project include the client... so one DLL for other solutions to import from, and it doesn't really add much of anything to the Server implementation. That's just one example. Another is separating API controllers, DAL, BLL into separate Projects... there's rarely a practical reason for this, and in practice just adds indirection and complexity for very little real world value. But hey, "Enterprise" patterns and all.