Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It griefed us with some conflicts in
Hudl.QueuedServices
with some Bclstuff. We don't really need it, either.
Also added two test WebApp projects to test that we retain context after
await
ing a call that has.ConfigureAwait(false)
called on it downstream.TestMvc40WebApp
was created targeting 4.0 and then given theaspnet:UseTaskFriendlySynchronizationContext
configuration value. Itstest/context
route should print "Success".TestMvc45WebApp
was created targeting 4.5 and has<httpRuntime targetFramework="4.5"/>
. Itstest/context
route should print "Success".I verified that
TestMvc40WebApp
instead throws aNullReferenceException
when the configured value is not present.