Tomáš Matoušek

Also I'd consider calling the target ```Test``` instead of ```VSTest```, to be consistent with ```dotnet test```.

@onovotny Check this one out: https://github.com/dotnet/roslyn-tools/blob/master/src/RepoToolset/Test.props https://github.com/dotnet/roslyn-tools/blob/master/src/RepoToolset/Test.targets You should be able to use these in your project.

(the .props file might not be needed)

We have made multiple changes to address `dotnet watch` reliability. If the issue still reproduces with the latest .NET 8 SDK preview, please reopen the issue with `--verbose` output, the...

I can't reproduce it but I see a couple potential issues with the current implementation. Fixing in https://github.com/dotnet/sdk/pull/35712

> What's the effect of placing CompilerGenerated on the constructor? It prevents the debugger from stepping in? CompilerGenerated has no effect on debugging.

Fixed by https://github.com/dotnet/roslyn/pull/68765

My guess is that there are two reasons for this: 1) https://github.com/dotnet/runtime/issues/75154 2) Caches in ASP.NET need to be invalidated. @davidwengier FYI

Any caches of endpoints that memoize MethodInfos

@drewnoakes I don't remember if it did. It only happens occasionally.