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

.NET 7 #247

Open
DSchougaard opened this issue Dec 22, 2022 · 7 comments
Open

.NET 7 #247

DSchougaard opened this issue Dec 22, 2022 · 7 comments

Comments

@DSchougaard
Copy link

It looks like the dotnet octo tool has a hard dependency on .NET 6. When running the microsoft .NET 7 docker image, running dotnet octo fails with the following error:

root@a59ab258ba76:/# dotnet octo --version
You must install or update .NET to run this application.

App: /root/.dotnet/tools/dotnet-octo
Architecture: x64
Framework: 'Microsoft.NETCore.App', version '6.0.0' (x64)
.NET location: /usr/share/dotnet

The following frameworks were found:
  7.0.0 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Learn about framework resolution:
https://aka.ms/dotnet/app-launch-failed

To install missing framework, download:
https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0&arch=x64&rid=debian.11-x64
@KennyEliasson
Copy link

KennyEliasson commented Jan 31, 2023

Just ran into this as well, any known work arounds?

@DSchougaard
Copy link
Author

@KennyEliasson Technically, yes. You can force dotnet to do a "roll forward" of versions:
https://learn.microsoft.com/en-us/dotnet/core/versions/selection

I've had success doing this by using the environment variable:
DOTNET_ROLL_FORWARD=major

So far Pack, Push and Create-Release commands all work fine for me, at the very least.

@KennyEliasson
Copy link

@DSchougaard Thank you so much for this! I had resorted to install .NET6 in my .NET7 SDK container to get it to work.

@DSchougaard
Copy link
Author

@KennyEliasson You're welcome :) To be honest, I admit I should have updated the issue the minute I found the workaround.

@gioleppe
Copy link

gioleppe commented Feb 9, 2023

@DSchougaard thanks Daniel you saved my day :)

Instead of setting the environment variable I just added the --roll-forward Major argument to all commands I was using

@olicooper
Copy link

Is there a timeline for this to be released?

@DSchougaard
Copy link
Author

@olicooper Given that the repository was updated with a sunset notice, 30th of January 2023, I unfortunately don't think it will be fixed:
1f580de

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

No branches or pull requests

4 participants