3 ms·
To play devil's advocate: merging csproj files is a PITA. It's too bad VS can't just read the file system to determine what files/namespaces are in a project li
by ld00d 11y ago
To play devil's advocate: merging csproj files is a PITA. It's too bad VS can't just read the file system to determine what files/namespaces are in a project like virtually everyone else does.
- alexc05 11y agoYou're right about the PITA, and they start out seeming like a wildly complicated and painfully documented dog's breakfast. I'm happy that .net CORE is moving to dynamic inclusion via "magic" However, once you are used to CSPROJ, they're actually ok to understand & merge. Additionally, if you're a c# shop, using msbuild & msdeploy gives you a lot more than hand rolling 100% of your compilation tools. If you stick to the framework, you save money. Occasional minor merge conflicts around file includes are minor relative the the ability to step-through-debug the code and get project wide code completion via intellisense.