Build toolchain. MSbuild performance sucks among other things. Also Consider VSTO build toolchain. We have to ship VS on build machines for example which is expensive and unnecessary. Even if we throw ridiculous IO capacity and CPU at build we hit a wall quickly where there is no return. On top of that managing framework upgrades across tens of solutions is a nightmare.
Roadmap schitzophrenia. The core is relatively stable. I’m talking about the ecosystem of abandonment over the last 10 years or so. See my post history for a list of just MSFT projects. Ancillary third party libraries in nuget also suffer from sudden disinterest from the maintainers and abandonment on a regular basis.
For your use cases it’s probably the least bad option but on the server side or the desktop these days I wouldn’t use it. Qt/ex/python on the desktop. Python or Go on the server side depending on the use case required.
The key thing is developer latency and maintenance cost. While the runtime performance is good the dev side of things is not. It gets expensive quick.