-
Notifications
You must be signed in to change notification settings - Fork 176
Always run on the latest Runtime #694
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.
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
Conversation
I like this approach |
7f6bd16
to
cc17cf1
Compare
527b5f2
to
5940a5c
Compare
There was an issue running on 3.0.1xx previews that did not allow 2.x apps to rollforward. Fixed in dotnet/sdk#3542 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -1,10 +1,13 @@ | |||
<Project Sdk="Microsoft.NET.Sdk"> | |||
|
|||
<PropertyGroup> | |||
<TargetFramework>netcoreapp3.0</TargetFramework> | |||
<TargetFramework>netcoreapp2.1</TargetFramework> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
did we mean to roll this back?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, since we are rolling forward I wanted running the unit tests to behave the same a running dotnet-format.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the roll forward should allow this to work without issue
As an alternative fix to the move to netcoreapp3.1, we could always run on the latest installed runtime. We were already rolling forward in cases when the requested runtime was not installed.