aspire icon indicating copy to clipboard operation
aspire copied to clipboard
verified publisher icon dotnet

Blazor WASM not working with Latest Aspire Preview 3

Open aherrick opened this issue 2 years ago • 12 comments

#296 mentioned this would be fixed in Preview 2. I'm on Preview 3 and still seeing this error.

There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'

Minimal Repo: BlazorApp1.zip

aherrick avatar Dec 07 '23 23:12 aherrick

Are you certain, that you are on Aspire preview 3? Would you run dotnet workload list in a cmd and validate that? Because I don't think preview 2 is released yet, you may be confusing the Aspire preview with the VS preview version.

JoschiZ avatar Dec 17 '23 16:12 JoschiZ

I'm on the daily bits:

image

aherrick avatar Dec 17 '23 21:12 aherrick

Aspire Preview 2 officially dropped today and this seems to still be a problem.

JoschiZ avatar Dec 25 '23 15:12 JoschiZ

This problem still going on, when will this problem be solved?

oguz687 avatar Jan 27 '24 02:01 oguz687

cc @joperezr

davidfowl avatar Jan 27 '24 22:01 davidfowl

is blazor wasm Standalone supported yet? or how do i then deploy it

SymoHTL avatar Jan 29 '24 13:01 SymoHTL

Blazor standalone is not supported. We might be able to make it work for development but not deployment (at least for the initial release).

davidfowl avatar Jan 29 '24 15:01 davidfowl

cc @vijayrkn I beleive later versions of VS will support Blazor WASM https://github.com/dotnet/aspire/issues/1418

davidfowl avatar Mar 09 '24 23:03 davidfowl

OR this might be a workload issue. @joperezr

davidfowl avatar Mar 09 '24 23:03 davidfowl

Not sure I'm following what seems to be wrong here. Original post is about Blazor wasm not working with Aspire, from the above it seems like this is expected, so not sure how that relates to the workload.

joperezr avatar Mar 11 '24 21:03 joperezr

Just got Microsoft Visual Studio Community V 17.10.0 Preview 3 There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'

I apologize if this is the wrong thread... please don't yell at me :)

kamabery avatar Apr 10 '24 18:04 kamabery

Still getting this error with current latest - Aspire GA.

The Problem is with the Service defaults project, it uses <FrameworkReference Include="Microsoft.AspNetCore.App" />, this pulls in Microsoft.AspNetCore.App which is not supported in webassembly.

You get things to build/run by removing the Service Defaults project reference from the web assembly app, but then you lose all the nice telemetry stuff (and service discovery?).

Lindsay-Mathieson avatar May 26 '24 05:05 Lindsay-Mathieson

What issues? Service discovery and dashboard telemetry doesn't work in WASM and that's not what this issue is about. I'll close this one, and we should open new issues with specific feature requests.

See https://github.com/dotnet/aspire/issues?q=is%3Aissue+is%3Aopen+blazor+wasm+

davidfowl avatar May 26 '24 16:05 davidfowl

What issues?

The one from the very first comment

There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'

Lindsay-Mathieson avatar May 26 '24 16:05 Lindsay-Mathieson

Ah I see, lets treat this one as a dupe of https://github.com/dotnet/aspire/issues/1536. There's much better information in there.

davidfowl avatar May 26 '24 16:05 davidfowl