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 apps using components cannot be debugged #1275

Closed
bwateratmsft opened this issue Sep 16, 2019 · 1 comment · Fixed by #1400
Closed

Blazor apps using components cannot be debugged #1275

bwateratmsft opened this issue Sep 16, 2019 · 1 comment · Fixed by #1400
Labels
bug .NET
Milestone
0.9.0

Comments

@bwateratmsft
Copy link
Contributor

Because Blazor writes a manifest file based on the host filesystem for where to find components (i.e. from NuGet packages and other projects in the solution), Blazor apps cannot be debugged, as our current model does build on the host and volume maps that into the container.
@bwateratmsft bwateratmsft mentioned this issue Sep 18, 2019
Closed
@bwateratmsft
Copy link
Contributor Author

bwateratmsft commented Sep 19, 2019 •
edited
Loading

Blocked by microsoft/vscode#80375

@bwateratmsft bwateratmsft added this to the Future milestone Sep 19, 2019
@bwateratmsft bwateratmsft modified the milestones: Future, 0.9.0 Oct 7, 2019
@bwateratmsft bwateratmsft mentioned this issue Oct 22, 2019
Merged
@bwateratmsft bwateratmsft mentioned this issue Nov 6, 2019
Merged
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug .NET
Projects
None yet
Milestone
0.9.0
Development

Successfully merging a pull request may close this issue.

Containerize Blazor static web assets manifest microsoft/vscode-docker
1 participant
@bwateratmsft