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.

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

Can no longer run standalone Blazor WebAssembly apps from source in this repo #31611

Closed
SteveSandersonMS opened this issue Apr 8, 2021 · 3 comments
Assignees
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug. Done This issue has been fixed
Milestone

Comments

@SteveSandersonMS
Copy link
Member

Repro:

  • cd src\Components\WebAssembly\testassets\StandaloneApp
  • dotnet run

Expected: App runs, as it used to
Actual:

A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'C:\path\artifacts\bin\Microsoft.AspNetCore.Components.WebAssembly.DevServer\Debug\net6.0\'.
Failed to run as a self-contained app.
  - The application was run as a self-contained app because 'C:\path\artifacts\bin\Microsoft.AspNetCore.Components.WebAssembly.DevServer\Debug\net6.0\blazor-devserver.runtimeconfig.json' was not found.
  - If this should be a framework-dependent app, add the 'C:\path\artifacts\bin\Microsoft.AspNetCore.Components.WebAssembly.DevServer\Debug\net6.0\blazor-devserver.runtimeconfig.json' file and specify the appropriate framework.

In combination with #31023 which TBH is much more impactful, I'm finding the productivity of working within our repo to be a real challenge at the moment. Am I the only one? If anyone has capacity to look into this before the end of preview 4 that would be great, or if not I think we need to reserve some time at the start of preview 5 to prioritise this ahead of feature/bug work.

@SteveSandersonMS SteveSandersonMS added the area-blazor Includes: Blazor, Razor Components label Apr 8, 2021
@pranavkm pranavkm added this to the Next sprint planning milestone Apr 8, 2021
@ghost
Copy link

ghost commented Apr 8, 2021

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@pranavkm
Copy link
Contributor

pranavkm commented Apr 8, 2021

@captainsafia if you're able to look at this as part of build ops, that would be great.

@captainsafia captainsafia added bug This issue describes a behavior which is not expected - a bug. and removed investigate labels Apr 12, 2021
@captainsafia
Copy link
Member

Should be fixed on the latest main.

@ghost ghost added Done This issue has been fixed and removed Working labels Apr 12, 2021
@ghost ghost locked as resolved and limited conversation to collaborators May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug. Done This issue has been fixed
Projects
None yet
Development

No branches or pull requests

3 participants