3 ms·
I've worked with a tonne of people in the industry like this, particularly in MS land where something is "impossible" if Visual Studio can't do it. Often you'll
by flukus 9y ago
I've worked with a tonne of people in the industry like this, particularly in MS land where something is "impossible" if Visual Studio can't do it. Often you'll end up with a million projects for namespacing because they don't know what a folder is.
It's only going to get worse as we have a generation of kids that have only used tablets and don't know what an "exe" is, or even a file.
- UK-AL 9y agoI find that multiple projects are heavily used in Visual studio, because a lot tooling works better by splitting into projects instead. NCrunch is the example here. It's easier to enforce dependency rules. A domain model should not have any dependencies on a specific technology, the easiest to way to enforce that is a separate project, with no references.