3 ms·
You know, in 2003 we (I'm the original author of CoreXT) had some attempts at a serious discussion of merging CoreXT + Razzle and whatever the VS team was doing
by dblock 12y ago
You know, in 2003 we (I'm the original author of CoreXT) had some attempts at a serious discussion of merging CoreXT + Razzle and whatever the VS team was doing. I was told "Windows is too big" and "Visual Studio is built for a different customer than Microsoft developers" and the "future is Team System".
Here we are 10 years later ...
- larsberg 12y agoHey! I was the one running the build environment stuff in VS at the time. IIRC, CoreXT didn't handle some really oddball scenarios we had that involved self-hosted compilers and runtimes. e.g., rerunning the build with the compiler you just built or just the runtime you just built, or... We were also trying to shift as much of the managed parts of the stack as possible to using MSBuild natively, which required a custom local runtime build to support asmmeta (which rudi and I created to solve the circular build dependencies in managed libraries in VS). We were also using subtly different versions of build.exe whose parallel build support and support for scenarios with files over 2^31 bytes differed in non-trivial ways. In the end, I think I stole everything I liked in CoreXT (which was a lot!) but we couldn't really adopt the workflow without breaking basic requirements that VS had that nobody outside of a compiler toolchain really sees. (BTW, I apologize if some of this is off. Like you pointed out, this is more than 10 years ago.)
- dblock 12y agoHeh! First, say hi when in NYC, dblock at dblock dot org. I think workflow, spirit and approach are the real deal. Everything else is just software :-)