Skip to content

Consider not using CreateDefaultBuilder in Blazor debugger-proxy #19909

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
Closed
pranavkm opened this issue Mar 16, 2020 · 2 comments
Closed

Consider not using CreateDefaultBuilder in Blazor debugger-proxy #19909

pranavkm opened this issue Mar 16, 2020 · 2 comments
Assignees
@captainsafia
Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly
Milestone
blazor-wasm-3.2-p...

Comments

@pranavkm
Copy link
Contributor

See #19767 (comment)
@pranavkm pranavkm added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Mar 16, 2020
@javiercn
Copy link
Member

I agree with el @Tratcher

@mkArtakMSFT mkArtakMSFT added this to the blazor-wasm-3.2-preview4 milestone Mar 17, 2020
@captainsafia captainsafia self-assigned this Mar 17, 2020
@captainsafia captainsafia mentioned this issue Mar 18, 2020
Merged
captainsafia added a commit that referenced this issue Mar 19, 2020
@captainsafia
Use custom DebugProxyHost to initialize DebugProxy config (#19980)
c7d3c1f 
Addresses #19909
@captainsafia
Copy link
Member

Closing this as it was resolved by #19980.

@mkArtakMSFT mkArtakMSFT added the Done This issue has been fixed label Mar 20, 2020
ghost pushed a commit that referenced this issue Mar 25, 2020
@pranavkm @SteveSandersonMS @captainsafia
Blazor wasm preview4 (#20117)
47536a3 
* Restore public API contract on WebAssemblyJSRuntime (#19968)

* Shrink icon-512.png (#19999)

* Use custom DebugProxyHost to initialize DebugProxy config (#19980)

Addresses #19909

* Spruce up WebAssemblyHostEnvironment interface and use (#20008)

* Load .dlls/.wasm/.pdb in parallel with dotnet.*.js. Fixes #18898 (#20029)

* Add BaseAddress property to WebAssemblyHostEnvironment (#20019)

- Adds `BaseAddress` to `IWebAssemblyHostEnvironment`
- Uses unmarshalled APIs to extract application host
- Move NavigationManager initialization to startup code
- Fix subdir mapping in ClientSideHostingTest

Addresses #19910

Co-authored-by: Steve Sanderson <[email protected]>
Co-authored-by: Safia Abdalla <[email protected]>
Co-authored-by: Safia Abdalla <[email protected]>
@ghost ghost locked as resolved and limited conversation to collaborators Apr 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@captainsafia captainsafia

Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly
Projects
None yet
Milestone
blazor-wasm-3.2-preview4
Development

No branches or pull requests
4 participants
@pranavkm @captainsafia @javiercn @mkArtakMSFT