-
Notifications
You must be signed in to change notification settings - Fork 10.3k
After upgrading to .NET Standard 2.1 and Blazor v3.1.0-preview4.19579.2, Blazor WebAssembly projects no longer work. #17619
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
Comments
@javiercn
|
@Rauce thanks for contacting us. I'm not sure what can be going on. I would suggest you first try to update to the latest released blazor version, which is preview4 and is built on top of the .NET Core 3.1.0 RTM |
I can confirm the new project I tested with is created targeting .NET Standard 2.1, with Nuget Blazor package versions v3.1.0-preview4.19579.2. .NET Core 3.1.0 RTM is installed. |
@pranavkm Based on this, this seems to be missing the application name, is that correct? |
FYI. If I revert my projects back to .NET Standard 2.0 and Blazor v3.1.0-preview3.19555.2 (while keeping VS2019 16.4.0 and .NET Core 3.1.0 RTM), they build and run without any issues. (I added this to original issue description). |
I think you can reproduce this by creating a new Blazor WebAssembly (ASP.NET Core Hosted) project (VS16.4, Latest Templates), via the VS UI, and try to rebuild the default generated Client project. |
Having issues too. Anyone got a workaround? |
Disabling linking on build seems to let me build right now.
|
Could one of you share a minimal project that reproduces the build error? I tried @simonpbond's suggestion
and haven't been able to reproduce the error. |
@pranavkm Reproduced project
|
Thanks! |
Still no luck. I tried running rebuild a couple of times on the BlazorRequestedRepo.Client project, tried rebuilding with changes to file and regular builds. All of these succeeded. Is there a specific sequence you're running? Here are a couple of things that would help
|
Possibly the same one as this one: |
Woohoo! @jspuij's solution in #17754 (#17754 (comment)) fixed this error - my project is working again. |
We'll use the other to track fixing this for the next release. |
Uh oh!
There was an error while loading. Please reload this page.
To rule out any project-specific issues, I followed the instructions at https://docs.microsoft.com/en-us/aspnet/core/blazor/get-started?view=aspnetcore-3.1&tabs=visual-studio to create a new clean Blazor WebAssembly project.
I can confirm the new project is created targeting .NET Standard 2.1, with Nuget Blazor package versions v3.1.0-preview4.19579.2.
After the project is created, without modifying any of the project files, I simply hit 'Start Debugging' in Visual Studio (2019 v16.4).
In the first build attempt I get the following single error:
If I then immediately immediately try 'Start Debugging' again, it builds without this error, but in the launched browser window the following error appears instead:
If I revert this project back to .NET Standard 2.0 and Blazor v3.1.0-preview3.19555.2, it builds and runs without any issues.
Here's the output of
dotnet --info
Any ideas?
The text was updated successfully, but these errors were encountered: