I'm developing a Blazor application and I'm running dotnet watch on it for the hot module reload properties. It works great and fast when it is a standalone project, but after I introduced a DTO project and a client project as dependencies, it looks the dotnet watch has to build the two extra projects on every reload (if I understand it correctly) and the reload is a lot slower. Is there any way to somehow cache the projects? Does something like Vite not do that for fast Hot module reload? Or am I doing something wrong or misunderstand the dotnet watch?
Maybe it's something to do with the projects it depends on, which in that case is just bad luck and I'll have to live with the slow reload.
I have looked at the official Microsoft doc. and couldn't find anything relevant, might have missed something? I have also tried the command:
dotnet watch run --no-dependencies
It seems like that the dependency projects is no longer build (they no longer appear in the cmd output) but it's still slow.
