Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Blazor WebAssembly Standalone does not launch with .NET 6 Preview3 #31791

Closed
apsthisdev opened this issue Apr 14, 2021 · 3 comments
Closed

Blazor WebAssembly Standalone does not launch with .NET 6 Preview3 #31791

apsthisdev opened this issue Apr 14, 2021 · 3 comments
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions feature-iis Includes: IIS, ANCM ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. Status: Resolved

Comments

@apsthisdev
Copy link

Describe the bug

Blazor WebAssembly Fails to launch with default hosting model (InProcess) after migrating to .NET6 Preview 3. This is working with .NET5.0.

To Reproduce

No custom code is needed to reproduce. Just create a new Blazor WebAssembly Standalone project from Visual Studio 2019.
image

Build it and run

You will getting the InProcess error,
image

Switch Project back to .NET5.0, everything works

image

Further technical details

  • NET SDK 6.0.100-preview.3
  • Visual Studio 16.10 Preview
@javiercn javiercn added area-runtime feature-iis Includes: IIS, ANCM labels Apr 14, 2021
@javiercn
Copy link
Member

@ameyasubhedar thanks for contacting us.

Does a new application also fail to run for you?

If you updated from 5.0 to 6.0 preview 3, can you compare that with a brand new application to see if you spot any difference?

@javiercn javiercn added the Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. label Apr 14, 2021
@pranavkm
Copy link
Contributor

Dupe of #30917. We fixed this in 6.0-preview4. In the meanwhile, running it without IIS should work.

@apsthisdev
Copy link
Author

@javiercn, yes a new application and old application both fails to run.

@ghost ghost added Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. and removed Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. labels Apr 14, 2021
@BrennanConroy BrennanConroy added the ✔️ Resolution: Duplicate Resolved as a duplicate of another issue label Apr 14, 2021
@ghost ghost added the Status: Resolved label Apr 14, 2021
@ghost ghost locked as resolved and limited conversation to collaborators May 21, 2021
@amcasey amcasey added area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions and removed area-runtime labels Jun 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions feature-iis Includes: IIS, ANCM ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. Status: Resolved
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@pranavkm @javiercn @BrennanConroy @amcasey @apsthisdev