Skip to content
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

Allow runtime roll-forward #232

Merged
merged 1 commit into from
May 1, 2019
Merged

Allow runtime roll-forward #232

merged 1 commit into from
May 1, 2019

Conversation

martincostello
Copy link
Contributor

Allow roll-forward to .NET Core 3.0 if 2.x is not installed as-per #205 (comment).

I think I've updated the right projects.

Allow roll-forward to .NET Core 3.0 if 2.x is not installed.
@danielpalme danielpalme merged commit d6a188c into danielpalme:master May 1, 2019
@martincostello martincostello deleted the Support-Runtime-Rollforward branch May 1, 2019 19:45
@danielpalme
Copy link
Owner

danielpalme commented May 5, 2019

New release is available here:
https://www.nuget.org/packages/ReportGenerator/4.1.5
https://www.nuget.org/packages/dotnet-reportgenerator-cli/4.1.5
https://www.nuget.org/packages/dotnet-reportgenerator-globaltool/4.1.5

@martincostello
Copy link
Contributor Author

I've just tried this out and it's now running for 3.0 projects.

@martincostello
Copy link
Contributor Author

Which then lead to this: https://github.com/dotnet/coreclr/issues/24402

@ViktorHofer
Copy link

Adding a roll-forward policy on max version is a very dangerous thing to do. A future version of .NET Core could easily break this. Have you considered instead cross-compiling?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants