Fix Microsoft.AspNetCore version in baseline

[dougbu]

• odd that Microsoft.AspNetCore.Server.IISIntegration didn't have correct version before…

[natemcmaster]

By chance, have you done anything to verify that we aren't missing any other out-of-date baseline entries?

[dougbu]

By chance, have you done anything to verify that we aren't missing any other out-of-date baseline entries?

I was about to do that. Wanted to get this fixed while it was in our faces 😸

[natemcmaster]

Will let @Eilon decide if this is a shiproom ask or tell.

[Eilon]

Definitely needs to go through shiproom because this affects what we ship. Please have the test ready in the PR, add the shiproom template to the top of the PR, and send mail.

[Eilon]

Oh and when you add the test, please run the test on the reverted files to see that it found what you found!

[dougbu]

Description

As described in #7546, the 2.1.8 release downgraded Microsoft.AspNetCore dependencies to version 2.1.6. This in turn leads to FileLoadExceptions as in #3503 (comment)

Customer impact

As one commenter said, we're entering ASP.NET Core version hell 😦

Users have multiple workarounds:

1. add <PackageReference Include="Microsoft.AspNetCore" Version="2.1.7" /> (NB: this is NOT the .App package)
2. Remove version from AspNetCore.App <PackageReference Include="Microsoft.AspNetCore.App" />
3. Update AspNetCore.App: <PackageReference Include="Microsoft.AspNetCore.App" Version="2.1.8" />

Regression?

Yes. Earlier 2.1.x releases did not have this issue.

Risk

Minimal. We are adding tests to ensure this issue does not occur going forward.

[vivmishra]

Approved for 2.1.9.