Browserlink causes "TypeLoadException" for 'Microsoft.AspNetCore.Http.Features.IHttpSendFileFeature' after RC2

[oiBio]

Describe the bug

After updating from RC1 to RC2 i get the following error. As the stacktrace implies its from the browserlink. And when i remove "app.UseBrowserLink()" from my middleware pipeline it works.

Any suggestions where my error is? I cant reproduce this in a minimal repo :-/

Exceptions (if any)

An unhandled exception occurred while processing the request.
TypeLoadException: Could not load type 'Microsoft.AspNetCore.Http.Features.IHttpSendFileFeature' from assembly 'Microsoft.AspNetCore.Http.Features, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
Microsoft.VisualStudio.Web.BrowserLink.BrowserLinkMiddleware.ExecuteWithFilter(IHttpSocketAdapter injectScriptSocket, string requestId, HttpContext httpContext)

Stack Query Cookies Headers Routing
TypeLoadException: Could not load type 'Microsoft.AspNetCore.Http.Features.IHttpSendFileFeature' from assembly 'Microsoft.AspNetCore.Http.Features, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
Microsoft.VisualStudio.Web.BrowserLink.BrowserLinkMiddleware.ExecuteWithFilter(IHttpSocketAdapter injectScriptSocket, string requestId, HttpContext httpContext)
System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start<TStateMachine>(ref TStateMachine stateMachine)
System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start<TStateMachine>(ref TStateMachine stateMachine)
Microsoft.VisualStudio.Web.BrowserLink.BrowserLinkMiddleware.ExecuteWithFilter(IHttpSocketAdapter injectScriptSocket, string requestId, HttpContext httpContext)
Microsoft.VisualStudio.Web.BrowserLink.BrowserLinkMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

Show raw exception details
System.TypeLoadException: Could not load type 'Microsoft.AspNetCore.Http.Features.IHttpSendFileFeature' from assembly 'Microsoft.AspNetCore.Http.Features, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
   at Microsoft.VisualStudio.Web.BrowserLink.BrowserLinkMiddleware.ExecuteWithFilter(IHttpSocketAdapter injectScriptSocket, String requestId, HttpContext httpContext)
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
   at Microsoft.VisualStudio.Web.BrowserLink.BrowserLinkMiddleware.ExecuteWithFilter(IHttpSocketAdapter injectScriptSocket, String requestId, HttpContext httpContext)
   at Microsoft.VisualStudio.Web.BrowserLink.BrowserLinkMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

Further technical details

.NET SDK (gemäß "global.json"): Version: 6.0.100-rc.2.21505.57 Commit: ab39070116

Laufzeitumgebung:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\6.0.100-rc.2.21505.57\

Host (useful for support):
Version: 6.0.0-rc.2.21480.5
Commit: 6b11d64e7e

.NET SDKs installed:
2.2.207 [C:\Program Files\dotnet\sdk]
3.1.200-preview-014977 [C:\Program Files\dotnet\sdk]
3.1.200-preview-015002 [C:\Program Files\dotnet\sdk]
3.1.300-preview-015048 [C:\Program Files\dotnet\sdk]
3.1.300-preview-015095 [C:\Program Files\dotnet\sdk]
3.1.302 [C:\Program Files\dotnet\sdk]
3.1.400-preview-015151 [C:\Program Files\dotnet\sdk]
5.0.100-rc.2.20479.15 [C:\Program Files\dotnet\sdk]
5.0.100 [C:\Program Files\dotnet\sdk]
5.0.201 [C:\Program Files\dotnet\sdk]
5.0.301 [C:\Program Files\dotnet\sdk]
5.0.302 [C:\Program Files\dotnet\sdk]
5.0.401 [C:\Program Files\dotnet\sdk]
5.0.402 [C:\Program Files\dotnet\sdk]
6.0.100-preview.4.21255.9 [C:\Program Files\dotnet\sdk]
6.0.100-rc.2.21505.57 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.19 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.0-preview.6.21355.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.0-rc.2.21480.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.19 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.0-preview.6.21352.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.0-rc.2.21480.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.19 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.8 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.0-rc.2.21501.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

[pranavkm]

FYI @jodavis

[jodavis]

@oiBio If you're using .NET 6, you no longer need the Browser Link module or app.UseBrowserLink() statement to use Browser Link in VS 2022. If the option "Tools->Options->Projects and Solutions->ASP.NET Core->CSS Hot Reload" is enabled, then Browser Link is automatically enabled for your project when launched from Visual Studio.

[jwbats]

@oiBio If you're using .NET 6, you no longer need the Browser Link module or app.UseBrowserLink() statement to use Browser Link in VS 2022. If the option "Tools->Options->Projects and Solutions->ASP.NET Core->CSS Hot Reload" is enabled, then Browser Link is automatically enabled for your project when launched from Visual Studio.

I have that option enabled, but browser link remains disabled for me. When I manually enable it, I get the same error as posted above.

I can't refresh linked browsers like this, and it's annoying.

[jodavis]

Hi @jwbats,

You should remove the Browser Link package and the app.UseBrowserLink() statement from your project. They you won't get errors whether or not Browser Link is enabled in Visual Studio.

If you try that and you're still not seeing a connection when Browser Link and CSS Hot Reload are enabled (you can check the Browser Link Dashboard in Visual Studio), please report feedback through Visual Studio. That will allow us to collect more information and investigate this specific issue.

[jwbats]

Tnx @jodavis. That solved the error. However, the 'Refresh Linked Browsers' shortcut option (CTRL+ ALT + ENTER) is grayed out. Unsurprisingly, the shortcut also doesn't work.

Any idea why that is and, more importantly, how I can fix it?

I'm developing vue components. Browser Link's css-sync feature isn't automatically picking up on the transpiled js files in my dest folder.

It would help if the shortcut worked.

[jodavis]

@jwbats Can you confirm whether the connection is showing up in the Browser Link Dashboard in VS?

If not, there are a few things you can check. First, there should be a <script> tag added to the bottom of your HTML file with a URL that ends in "/browserLink". If that's there, then you can look at the Network tab in your browser's dev tools to see if the script was downloaded successfully. And if that was successful, you can check the browser's Console tab to see if any errors were reported from the script.

If there are any connections, then the command should be enabled. The logic to enable it is as simple as Enabled = refreshTargets.Any().

(Apologies for the delay, I was in training all week and I'm catching up.)

[jwbats]

@jodavis

The connection isn't shown in the BrowserLink tab.

I'll consult the docs related to BrowserLink, to see if I missed something. If I can't find anything, I'll report it as a bug.

Thanks for your time.

[jwbats]

Here's the official docs, in .net 6 view.

It says to use the app.UseBrowserLink() statement. How could it ever work without having that statement? I probably also need the package.

That will put me back on square 1, probably giving me my error back.

Where does the idea come from, that Browser Link will work on .NET 6 without the package and the statement?

[jodavis]

@jwbats The documentation is out of date. (I'll follow up on that.) In a late preview of VS 2022, we added the CSS Hot Reload feature, which basically adds the Browser Link package and activates it without needing to explicitly reference it in the project. The package that VS adds is newer, and doesn't have the issues that the older published package has.

Did you have a chance to see if the <script> tag appears in your page, and that it's downloading successfully?

[jwbats]

@jodavis There is no mention of 'browserLink' in the source page.

I recall having another problem with it, back when you needed to UseBrowserLink() call. I had put it in the wrong order in my startup. It needed to become after UseResponseCompression(), instead of before.

It resulted in the same: not making an appearance on the source page and, therefore, also no connection / not working.

Now that this use-call doesn't have to be made anymore, I have no idea where in the middleware pipeline it puts itself.

This 'newer package' that you say VS 2022 adds... can I somehow verify that it is correctly installed? I see no references to it in my project at first glance.

[OFark]

It's still affected by the HTTPS (which is Default) protocol and not having a certificate, so your browser will shun the browserlink.js file. See my SO post here: https://stackoverflow.com/a/68960152/1109858

TL;DR;
Inspect your browser's console, find the "OMG I can't download browserlink", get the URL, load the URL in a new tab, accept the security warning and continue. Go back to your page.