-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
S.N.Quic private #54610
S.N.Quic private #54610
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBased on mail with @ericstj set up S.N.Quic to be flown to ASP. I still see the S.N.Quic in There's still the ASP.NET part that needs to be solved afterwards. cc: @wtgodbe @JamesNK @ViktorHofer @wfurt @CarnaViire @geoffkizer
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBased on mail with @ericstj set up S.N.Quic to be flown to ASP. I still see the S.N.Quic in There's still the ASP.NET part that needs to be solved afterwards. cc: @wtgodbe @JamesNK @ViktorHofer @wfurt @CarnaViire @geoffkizer
|
I just tried that and I got compilations errors:
I assume that the ref is now not produced, but that means that even our own libraries cannot see it? |
The ref is produced but it now isn't binplaced into the directory that marks the Microsoft.NETCore.App.Ref targeting pack anymore, as expected. The failure is because now that System.Net.Quic isn't part of the targeting pack anymore, a simple |
@ViktorHofer thanks! That worked! |
@@ -629,7 +629,7 @@ | |||
<Reference Include="System.Net.NameResolution" /> | |||
<Reference Include="System.Net.NetworkInformation" /> | |||
<Reference Include="System.Net.Primitives" /> | |||
<Reference Include="System.Net.Quic" /> | |||
<ProjectReference Include="..\..\System.Net.Quic\ref\System.Net.Quic.csproj" /> |
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.
nit: please move this up to the other ProjectReference as we usually sort alphabetically. Also use the $(LibrariesProjectRoot)
property instead of ..\..\
.
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.
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.
LGTM
This needs to be removed: runtime/src/libraries/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/SocketsHttpHandler.cs Line 400 in c0ed319
|
@@ -3,6 +3,7 @@ | |||
<PropertyGroup> | |||
<StrongNameKeyId>Microsoft</StrongNameKeyId> | |||
<IncludePlatformAttributes>true</IncludePlatformAttributes> | |||
<IsAspNetCoreApp>true</IsAspNetCoreApp> |
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.
What exactly does this control? We don't want this .dll to be part of our SharedFx/Targeting Pack
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.
Quoting @ericstj from the mail since I do not understand the process fully:
Today this is used to bundle public API which ships in ASP.NET but builds in dotnet/runtime. This allows us to avoid putting those builds in our public packages while still giving them reference assemblies and 6.0 targeted assemblies.
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.
@wtgodbe if putting it into the transport package the same way as the other libraries that form the ref/runtime packs, you will likely need to exclude this one from automatically flowing in your infra.
Good catch! The easiest way ATM would be to just make it internal and set it via reflection in our tests here: Line 52 in 0416c34
I know that @geoffkizer wanted to keep the mock implementation for testing purposes, which uses this settings. So I guess I cannot get rid of it completely. Any thoughts @stephentoub @geoffkizer? |
At this point, I'd have hoped the mock implementation would have outlived its usefulness and we could just nuke all of this. But I'll go with whatever Geoff prefers here. |
Failures are unrelated. |
Based on mail with @ericstj set up S.N.Quic to be flown to ASP.
I still see the S.N.Quic inartifacts/bin/ref/net6.0
. How do I actually make it "private", i.e. to not publish ref assembly? @Anipik could you please help?Fixed with @ViktorHofer help. So I guess this is it for runtime.
There's still the ASP.NET part that needs to be solved afterwards.
Contributes to #54534
cc: @wtgodbe @JamesNK @ViktorHofer @wfurt @CarnaViire @geoffkizer