Skip to content

Update 3.1 to Jan2019 release. #1464

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Feb 27, 2020
Merged

Update 3.1 to Jan2019 release. #1464

merged 1 commit into from
Feb 27, 2020

Conversation

crummel
Copy link
Contributor

@crummel crummel commented Jan 28, 2020

No description provided.

@dagood
Copy link
Member

dagood commented Feb 4, 2020

I've added a commit that ports the change to enable ASP.NET Core crossgen from #1446 to this branch. It turns out the patch is necessary in 3.0, but not 3.1, so it would appear we can simply re-enable crossgen in the 3.1 branch. Helps fix #1452 everywhere, not just 3.0.

@adaggarwal
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@crummel crummel force-pushed the release/3.1-jan2019 branch from cbff58a to 7a1a1cc Compare February 26, 2020 22:37
@crummel crummel merged commit 8ffc4e5 into dotnet:release/3.1 Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@crummel @dagood @adaggarwal