You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.
Remove the package dependency from Microsoft.AspNetCore.Server.Kestrel to Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.
This will break those who only depend on the Microsoft.AspNetCore.Server.Kestrel package and who call WebHostBuilderLibuvExtensions.UseLibuv(). These users can fix their projects by re-adding the dependency to libuv.
To minimize the number of 2.0 users that this will break, we should keep Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv in the dependency graph of Microsoft.AspNetCore.All.
Correct you won't be broken. No, .All doesn't directly reference "Libuv", but it does directly reference "Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv", so you still get the Libuv package transitively in .All
Related issue: #2360
Remove the package dependency from Microsoft.AspNetCore.Server.Kestrel to Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.
This will break those who only depend on the Microsoft.AspNetCore.Server.Kestrel package and who call
WebHostBuilderLibuvExtensions.UseLibuv()
. These users can fix their projects by re-adding the dependency to libuv.To minimize the number of 2.0 users that this will break, we should keep Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv in the dependency graph of Microsoft.AspNetCore.All.
Design meeting notes from March 2, 2018
/cc @halter73 @davidfowl @muratg
The text was updated successfully, but these errors were encountered: