3 ms·
We had to build tooling to break out solutions into multiple working solutions for use in VS and then use the actual solution for the build system. This meant t
by sokoloff 5y ago
We had to build tooling to break out solutions into multiple working solutions for use in VS and then use the actual solution for the build system. This meant that people would often break the build by modifying their local solution but not understanding what was really going on in the central build.
Our cutoffs were way smaller than 50 projects and 10K source files, though! (We had a lot of generated code, which we eventually mostly switched from generating code to generating MSIL directly to save the IDE.)
- fsfod 5y agoI wonder if filtered solutions files that load only the requested projects in a solution would of made that less painful https://docs.microsoft.com/en-us/visualstudio/ide/filtered-solutions?view=vs-2022#solution-filter-files https://docs.microsoft.com/en-us/visualstudio/ide/filtered-s...
- sokoloff 5y agoIt definitely would have; unfortunately, that was introduced in VS2019 and we had the need a decade before that, but glad to see that a better solution is now available.