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

dotnet 7 support? #692

Closed
brad-jones opened this issue Nov 9, 2022 · 6 comments
Closed

dotnet 7 support? #692

brad-jones opened this issue Nov 9, 2022 · 6 comments

Comments

@brad-jones
Copy link

Just wondering if there are any plans for dotnet 7 support given its now GA.

https://devblogs.microsoft.com/dotnet/announcing-dotnet-7/

@filipw
Copy link
Member

filipw commented Nov 9, 2022

Yes we will release very soon, the support is already there just based on the RC.
Once #693 is merged, we can go.

@vitaliy-orlov
Copy link

Hi! Any news? I see that #693 has already merged

@seesharper
Copy link
Collaborator

We are working on the final bits. We will release within the next week

@seesharper
Copy link
Collaborator

Version 1.4.0 with support for .Net7 has just been released

@vitaliy-orlov
Copy link

Thanks a lot!

@enricobenedos
Copy link

enricobenedos commented Jan 17, 2023

Today I've installed dotnet script CLI on my Mac and there was no way to keep intellisense working on VS Code..
Finally I understand that the issue was .NET 7, so I changed omnisharp.json from

{
  "script": {
    "enableScriptNuGetReferences": true,
    "defaultTargetFramework": "net7.0"
  }
}

to

{
  "script": {
    "enableScriptNuGetReferences": true,
    "defaultTargetFramework": "net6.0"
  }
}

I understand that it is not directly related with this CLI but I would like to post it here for people that like me have been lost a lot of time to understand if the problem was related to dotnet script.

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

5 participants