-
Notifications
You must be signed in to change notification settings - Fork 939
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
Support .netstandard2.0 #237
Conversation
SendAsync and ReceiveAsync now frequently return synchronously even if successful. These cases had not been properly handled yet, previous versions never hit these codepaths.
Integrate a library only build
Need to run a CTT pass on .NetStandard 2.0 ref server while we are waiting for CTT certification... |
@@ -1,7 +1,8 @@ | |||
<Project Sdk="Microsoft.NET.Sdk"> | |||
|
|||
<PropertyGroup> | |||
<TargetFramework>netstandard1.4</TargetFramework> | |||
<TargetFrameworks>net46;netstandard1.4;netstandard2.0</TargetFrameworks> | |||
<DefineConstants Condition="'$(TargetFramework)' == 'netstandard2.0'">$(DefineConstants);NO_HTTPS</DefineConstants> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why turn off HTTPS support for .Net Standard 2.0?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kestrel 2.0 doesn't compile yet. HTTPS is an extra work item for .Net Standard 2.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
tested with Ua Expert against standard and ref server
-Fix a bug in the TCP channel when .NetStandard2.0 uses synchronous return from SendAsync/ReceiveAsync, these cases were not properly handled and never called complete.
-build related fixes to support net46/uap/netstandard1.4 in one tbd nuget packet
-fix appveyor/travis builds