You should be able to work on one microservice at a time, run tests on them, and then wrap things up and work on another one. If you need to work on all of them

You should be able to work on one microservice at a time, run tests on them, and then wrap things up and work on another one. If you need to work on all of them at the same time that means that you managed to couple them together. In that case they're no longer true microservices, just spaghetti. Then, with .NET it is much easier to end up with gigantic spaghetti solutions with projects that are all coupled to each other. Coupling is the problem, learn to control coupling. If everything needs to know about everything, how do you expect to have a team that is capable of maintaining that?