Feels like it’s time for a .NET tooling renaissance.Solution files are dated, and project files while much cleaner, are tied to the powerful but flawed msbuild. We’ve seen huge performance improvements in runtime performance but haven’t done the same on the tooling side. #dotnet
Getting the build system right is hard (trust me, we tried hard). It needs to be fully incremental, *and* it needs to work with our IDE/Editor experiences. It also needs to interoperate with the existing system. People have large solutions that support C++, C#, installer projects
I want to be able to walk up to any .NET repository and know how to build it. Today it’s a dumpster fire. I love that go and rust tackled this OOTB (rust did a better job). Any modern language should come with a build and package management system.
You can follow @davidfowl.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:

By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.