@DustinCampbell ptal

@tmat How does loading the dll from VS change anything? You'll pick different dlls depending on the target framework?

You'll pick different dlls depending on the target framework?

We don't need different versions. The code is targeted to net6.0.
If we needed to multi-target to net11.0 in future we would just include both net6.0 and net11.0 in VS and pick the right one depending on the app TFM.

The important thing is that both sides of the client-server protocol (client: IDE, server: middleware) ship in the same product (VS or VS Code) and thus can be both updated at the same time without regard of any prior versions of VS or SDK.

@tmat thanks for the clarification.

At some point in 11.0 I would like us to revisit how the current BrowserRefresh injects things into the project (specially the JS script) as it has created a lot of headaches for us in the last couple of releases.

Ideally, we would want this functionality to better integrate with the existing infrastructure to extend Blazor/Razor/MVC, potentially participating from the build process.

Do you think moving the injection into VS will preclude us from doing that in any way?

Do you think moving the injection into VS will preclude us from doing that in any way?

On contrary, it will make it much easier.