blazorboilerplate | Blazor Boilerplate / Starter Template with MudBlazor | Binary Executable Format library

[Final update 07.12.2020 23:50 --> for everyone seeking for the anwser]

You are probably adding some nuget package which has in fields DEPENDENCIES .NET Core 3.1. For example Serilog.AspNetCore 3.4.0. In this very example you can include Serilog.AspNetCore 3.2.0 because it has in DEPENDENCIES only .NetStandard 2.0. See more explanation in @Ogglas answer.

There is not enough space on earth to ask the one and only question: "Why, o why Microsoft?":) The message is not clearly correlating issue with the solution - this is the lightest euphemism i am capable of making :)

For me, Blazor is very promising but it is still more a beta version. And not only for me. The startblazoring guys are claiming, that Blazor can be fickle sometimes. And I cannot agree more;) I am keeping finger crossed for it. But I suppose it would be a "ready product" only after .NET 6.0.

[Original Topic]

This is so frustrating :)

I hate errors, when I cannot simply interact and understood where it is coming from. I know, I am ignorant, and If I would pay more attention to "how is the blazor app created" I would understand in eye blink.

But for now it is only frustrating. What is? The error message:

Severity Code Description Project File Line Suppression State Error NETSDK1082 There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'. TestBlazorAppNoRuntimeError.Client C:\Program Files\dotnet\sdk\5.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets 387

Really, what can you fix here?:D Ehhhhh. I understand that .NET 5 is a "new thing". I understand Blazor is a "new thing" But really? It is really easy to "break" ;) (with a message that is saying nothing)

So what did I do?

Did I create very complicated project with hundreds of thousands of files?

No

Did I add hundreds of thousands of nuget packages.

No

All it takes is to create Blazor Webassembly app and add one nuget package to the shared (common) library (FYI: IdentityServer4 package). That is all folks. Kudos if you would now, that this package specificly is causing this issue (because i found out only by mistake):

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

Really, there is a great correlation here: between the error message and the package being added (this was sarcasm if anyone missed it:) )

So if you want to reproduce it create create "Blazor Webassembly":

I don't suppose the options chosen are making the difference. But if this is the case - you can see what option I did choose. Then just add IdentityServer4 nuget package to shared library:

https://www.nuget.org/packages/IdentityServer4/

That is all

If you are too lazy - download this project and check for yourself:

https://ufile.io/751l5wgq

I saw hundreds of SOF topics regarding this message:

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

But none of those was so easy to reproduce.

Why I am creating this topic?

Because I did try to implement (by copy-pasting to my solution) what guys did create in Blazor boilerplate here: https://github.com/enkodellc/blazorboilerplate

At the beginning, by mistake, I've added Identity4 NuGet instead of Identity4.storage and that is why I did observe such behavior (such error) and did correlate this package with this error. When I rolled back from Identity4 to Identity4.storage everything was correct once again. But after that I did a lot of code transfer from this repository. And once I've ended, right now, everything is compiling but once again I have:

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

And it is driving me crazy. Maybe you would have some idea, how to find out WHAT is causing this error (exactly the same as previously Identity4 nuget package was causing it)

[UPDATE 06.12.2020 12:30]

The question here is more: "Why is it happening and how to locate package causing the issue" I know that I can second guess what is causing this message to appear.

I did a little investigation. This error is showing in this target: