Skip to content
This repository was archived by the owner on Feb 25, 2021. It is now read-only.

Conversation

@kjpou1
Copy link

@kjpou1 kjpou1 commented Jun 21, 2019

Incorporating libraries necessary to start using mono's HTTP handler and WebSocket interfaces.

Proposal for discussion.

kjpou1 added 2 commits June 21, 2019 07:20
- Update `HowToUpgradeMono.md` with build instructions.
- Update build projects to include the framework libraries
- Add `MonoWasmFrameworkPath` to `.props`
@danroth27
Copy link
Member

Fixes dotnet/aspnetcore#10489

@SteveSandersonMS
Copy link
Member

Thanks for this, @kjpou1!

I took the approach here and included it in #1923. I changed the approach slightly in that it doesn't make sense to expose the framework libs as runtime references (i.e., in lib/netstandard1.0) because this package (Microsoft.AspNetCore.Blazor.Mono) isn't a runtime reference for apps anyway - it's only a build-time reference, so app developers still wouldn't obtain references to these packages. Longer term we should definitely look at making packages like WebAssembly.Bindings into published things that people can directly reference from their apps if they want.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants