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.0 GA #7939

Closed
dcwhittaker opened this issue Nov 8, 2022 · 15 comments
Closed

.NET 7.0 GA #7939

dcwhittaker opened this issue Nov 8, 2022 · 15 comments

Comments

@dcwhittaker
Copy link
Member

dcwhittaker commented Nov 8, 2022

Release Notes

7.0.0

Status

Asset Type 7.0.0 Notes
Installers/Binaries
Container Images
(Linux)
Container Images
(Windows)
Winget Packages
Snaps
Linux Packages (Microsoft distribution)
     Centos 7
     Debian 10
     Debian 11
     Fedora 35
     Fedora 36
     OpenSUSE 15
     Ubuntu 18.04
     Ubuntu 20.04
     Ubuntu 22.04

Please report any issues you find with .NET 7.0, either responding to this issue, creating a new issue or creating a new issue in one of the following repos:

Known Issues

If there are any issues with this release we will track them here and check issues off as they're resolved. See the linked issues for details on progress and resolution details.

* Linux packages are delayed in publishing for 7.0

@mfisher214
Copy link

Hello, I am running into an issue where after updating to .NET 7, my coverlet output path is being ignored

dotnet test command I am using:
dotnet test --no-build --configuration release /p:CollectCoverage=true /p:CoverletOutput=../CoverageResults/ /p:MergeWith="../CoverageResults/coverage.json" /p:CoverletOutputFormat="opencover,json" -m:1

After updating projects from .NET 6 to .NET 7, the coverage output paths change to the following:

Old: '/home/vsts/work/_temp/coverage/coverage.json'
New: '/home/vsts/work/1/s/tests/dotnet/(project directory)/coverage.json'

This is causing our azure pipeline builds to fail sonar test coverage tollgate because coverage files are not where they are expected to be. Is there something I'm missing here?

@leecow
Copy link
Member

leecow commented Nov 9, 2022

@marcpopMSFT - any ideas for @mfisher214 above?

@khteh
Copy link

khteh commented Nov 9, 2022

How to install on Ubuntu 22.10?

@GREsau
Copy link

GREsau commented Nov 9, 2022

@mfisher214's problem looks like coverlet-coverage/coverlet#1391 / microsoft/vstest#4014

@marcpopMSFT
Copy link
Member

@baronfel as I believe 4014 is fixed by dotnet/sdk#27961 which will release in 7.0.101

@SeanFarrow
Copy link

Good morning,

Has a diff been published between .Net 6 and 7?
There doesn't appear to be anything inthe core repo, so thought I'd ask.

Thanks for a really good release.

Sean.

@TehNolz
Copy link

TehNolz commented Nov 15, 2022

Any ETA for the Linux packages?

@ghost
Copy link

ghost commented Nov 16, 2022

What is the best way to install it on ubuntu 22.04 x64 and arm64? dotnet-install.sh or something else?

@D4nyi
Copy link

D4nyi commented Nov 18, 2022

Any update on when will the updates (.NET 6.0.11 and .NET 7.0.X) be available on Ubuntu 22.04 LTS package feed?

@marcpopMSFT
Copy link
Member

@rbhanda for any updates.

@dcwhittaker
Copy link
Member Author

Chatted with @leecow and it looks like our 22.04 repo has the updates. As long as folks follow the guidance in #7699 they should see 7.0.0 and 6.0.11.

@ghost
Copy link

ghost commented Nov 19, 2022

Ok, it's here. But not on ubuntu package. But I thought it will be in default ubuntu feed.
You need to add this before.
wget https://packages.microsoft.com/config/ubuntu/22.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
rm packages-microsoft-prod.deb

image

But still, it's doesn't work for ARM version, this is raspbery pi 4 with Ubuntu Server 22.04 and it's not here. You need to install it manual.

image

@EatonZ
Copy link

EatonZ commented Nov 30, 2022

Where is the API diff between 6.0 and 7.0? I can't seem to find it.

@MaceWindu
Copy link

@EatonZ #7976

@dcwhittaker
Copy link
Member Author

Closing in favor of #8037

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

No branches or pull requests