If versioning is the only problem encountered in 6 months, I call it a good platform to work with!

When you get your project running as expected, the velocity is really good.

actually I had more problems than that.. I even raised some at their issue tracker.

Currently if you load a dotnet web application it will only load all needed assemblies on the first request, so if you have a ton of libraries that your first request will hit, it will load all of them. that's even worse than anything else so far. (actually you can write a assembly loading logic for that, but wtf?)

modularity is not prepackaged into .net core MVC/WebAPI. you can make assemblies that can make use of others, but it gets way way way way way way way trickier if you have 10 MVC projects linked together and every app has his own controllers/views/models/wwwroot/routing which will be merged together. (you need to load stuff via .Assembly, feels hacky (https://github.com/thiennn/trymodular/blob/master/Modular/sr...) uses xproj not csproj tough)

Next time I hear someone talk about "JS fatigue" I'm showing them this.