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

Request/Proposal for Clientside Bedrock to target .NET Standard 2.0 #89

Open
Ninds opened this issue Feb 22, 2020 · 1 comment
Open

Comments

@Ninds
Copy link
Contributor

Ninds commented Feb 22, 2020

For me the use case of Bedrock is to implement a server with some bespoke protocols. Essentially an ASP.NET Core for protocol X rather than HTTP.
This I am keen to do against .NET CORE 3.X.

However, since I have non-standard, inhouse protocols, I also have to make available clients. The constraint on clients to be built against .NET CORE is not feasible. An example of a client would be an Excel XLL, or some other older software built against .NET Framework 4.X.

Is this a reasonable request ? If so will it be considered.

As of right now I am using MG's "not so Unofficial" Unofficial library.
ConnectionContext is available in a .NET Standard 2.0 compatible Nuget package. I did have to copy over DuplexPipe from Bedrock and inline it into my Clientside library.

@davidfowl
Copy link
Owner

Yes I plan to fix the TFMs as part of the MVP. #49

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants