Bolero icon indicating copy to clipboard operation
Bolero copied to clipboard

PSA: Template only works with latest .NET Core SDK (3.1.201)

Open brikken opened this issue 4 years ago • 9 comments

If you - like me - was lagging behind with just 3.1.0, you get a hard-to-understand build error.

Upgrading to latest Visual Studio or .NET Core SDK solves the problem.

brikken avatar Apr 04 '20 17:04 brikken

Yes, if I'm not mistaken it works with version 3.1.2 of the netcore runtime, so SDK version 3.1.102 or 3.1.200 (or higher).

Tarmil avatar Apr 04 '20 18:04 Tarmil

Not sure what is going on but last week everything was fine, this week I have installed VS Preview, and possibly updated sdk and VS (not preview) and now I am not able to run fsbolero. I spend last two hours on uninstalling and reinstalling VSs and SDKs but nothing help. Version 3.1.200 also doesn't work.

image

Any ideas what could be wrong or how to debug the issue?

Thanks in advance!

rbrus avatar Jul 15 '20 05:07 rbrus

Well, now that Bolero references Blazor 3.2, the minimal SDK required is actually 3.1.301.

I see that they released Blazor packages 18 hours ago, maybe that's related?

Tarmil avatar Jul 15 '20 08:07 Tarmil

I think this might be it.

I have changed references in the project file to: <PackageReference Include="Bolero" Version="0.13.23" /> <PackageReference Include="Bolero.Build" Version="0.13.23" /> <PackageReference Include="Bolero.HotReload" Version="0.13.8" /> <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.Build" Version="3.2.0" /> <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="3.2.0" /> And now it works, finally.

rbrus avatar Jul 15 '20 08:07 rbrus

Hmm, now I am running on the correct versions and using client-server (template) project - not client only, and I am receving the same issue:

image

I am trying to find out where this comes from also in the bolero project but no clue for now. Anybody anything?

rbrus avatar Jul 16 '20 10:07 rbrus

What is PSA?

Happypig375 avatar Jul 16 '20 10:07 Happypig375

@Happypig375 Public Service Announcement

panesofglass avatar Jul 18 '20 00:07 panesofglass

Thanks

Happypig375 avatar Jul 18 '20 03:07 Happypig375

@rbrus The issue is caused by Microsoft.AspNetCore.Components.WebAssembly.Build 3.2.1. If you set just this package to 3.2.0, the problem should go away.

Tarmil avatar Jul 18 '20 12:07 Tarmil