Blazor 0.8.0 standalone project that was generated by dotnet new blazor
command could not launch.
Steps to reproduce the behavior:
dotnet new -i Microsoft.AspNetCore.Blazor.Templates::0.8.0-preview-19104-04
dotnet new blazor
.dotnet build
. (this will be success.)dotnet run
The specified framework 'Microsoft.AspNetCore.App', version '3.0.0-preview-19104-06' was not found.
dotnet run
launch blazor server successfully.
The hosted version of Blazor 0.8.0 that was generated by dotnet new blazorhosted
CLI works fine.
I could not find the version 3.0.0-preview-19104-06 of .NET Core SDK or Runtime in my internet searching.
I rewrited "%HOME%.nuget\packages\microsoft.aspnetcore.blazor.cli\0.8.0-preview-19104-06\lib\netcoreapp3.0\dotnet-blazor.runtimeconfig.json" to use v.19075-0444 instead of v.19104-06.
After that, "dotnet run" works fine.
The Blazor standalone project that was generated by Visual Studio 2019 Preview 2.x worked fine.
The difference of theses projects was bellow:
<!-- from "dotnet new blazor"-->
<DotNetCliToolReference Include="Microsoft.AspNetCore.Blazor.Cli" Version="0.8.0-preview-19104-06" />
```xml
I tried uninstall the project template with `dotnet new -u Microsoft.AspNetCore.Blazor.Templates -Version` command, and reinstall it with `dotnet new -i Microsoft.AspNetCore.Blazor.Templates::0.8.0-preview-19104-04` command.
After that, `dotnet new blazor` generate the csproj as bellow:
```xml
<!-- from "dotnet new blazor" after reinstall project template -->
<DotNetCliToolReference Include="Microsoft.AspNetCore.Blazor.Cli" Version="0.8.0-preview-19104-04" />
Of course, Version 0.8.0-preview-19104-04 CLI works fine.
I'm not sure about why my first installation of Blazor project template for dotnet CLI was configured for using invalid version"19104-06".
Thanks for contacting us, @jsakamoto.
Glad you've found the cause of this and managed to fix it.
@danroth27, what this could be caused by?
@jsakamoto I suspect when you installed the Blazor templates initially you somehow picked up a version of the templates package from one of our MyGet feeds with dev builds.
Since you've resolved your own issue I'm going to go ahead and close this.