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
Http.Abstractions – HttpContext (abstract), referenced by middleware, Http, and applications
Http – DefaultHttpContext (implementation), referenced by Hosting (no change)
Http.Features – Feature interfaces & POCOs, referenced by Http and Servers
Note that all of these items are use the Http namespace, there are no Abstractions or Features namespaces.
The text was updated successfully, but these errors were encountered:
Is there a good way to know when everything's been rebuilt with changes like this? Ran into an issue this morning where unlocked deps caused a few broken builds and some cursing while I figured out that something was pulling in the old Http.Core package.
I ended up grabbing known good project.json files from our build server and locking them in place to prevent further breakage, but checking periodically for unbroken builds by unlocking the packages and letting updates happen isn't my idea of a good time.
RE:
aspnet/HttpAbstractions#295
#8
Http.Abstractions – HttpContext (abstract), referenced by middleware, Http, and applications
Http – DefaultHttpContext (implementation), referenced by Hosting (no change)
Http.Features – Feature interfaces & POCOs, referenced by Http and Servers
Note that all of these items are use the Http namespace, there are no Abstractions or Features namespaces.
The text was updated successfully, but these errors were encountered: