Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microsoft.AspNetCore.Blazor.Http.WebAssemblyHttpMessageHandler.SendAsync throws on Server Side Blazor #10329

Closed
AdmiralSnyder opened this issue May 17, 2019 · 1 comment
Labels
area-blazor Includes: Blazor, Razor Components

Comments

@AdmiralSnyder
Copy link

Describe the bug

On Server-Side Blazor, calling Microsoft.AspNetCore.Blazor.Http.WebAssemblyHttpMessageHandler.SendAsync
throws an exception, because
"Blazor._internal.http.sendAsync" is being invoked with Mono.WebAssembly.Interop.MonoWebAssemblyJSRuntime.InvokeUnmarshalled
giving the error "Generic method or method in generic class is internal call, PInvoke, or is defined in a COM Import class."

To Reproduce

Steps to reproduce the behavior:

  1. Using this version of ASP.NET Core 'Blazor 3.0.0-preview5-19224.8'
  2. Invoke Microsoft.AspNetCore.Blazor.Http.WebAssemblyHttpMessageHandler.SendAsync

Expected behavior

if WebAssemblyHttpMessageHandler isn't supposed to work on server-side, an exception should be thrown at instanciation time.
the xml comment only states:
///


/// A browser-compatible implementation of
///

@mkArtakMSFT
Copy link
Member

Thanks for contacting us, @AdmiralSnyder.
Feel free to send us a PR, and we'd happily consider it.
In the meantime this area is going to improve pretty soon as we move to the built-in Mono provided message handler.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Development

No branches or pull requests

3 participants