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 RC 1 #7800

Closed
dcwhittaker opened this issue Sep 14, 2022 · 13 comments
Closed

.NET 7.0 RC 1 #7800

dcwhittaker opened this issue Sep 14, 2022 · 13 comments

Comments

@dcwhittaker
Copy link
Member

dcwhittaker commented Sep 14, 2022

Release Notes

Please report any issues you find with .NET 7 RC1, 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.

@DoomerDGR8
Copy link

Hi!

Congrats on the release.

Immediately, the RegexGenerator attribute is not getting resolved. Packages are updated and also the global.json too.

image

[RegexGenerator("[(?*\",\\\\<>&#~%{}+$^@.\\s:\\/!;)]+")]
private static partial Regex FileFolderNameInvalidCharacterRegex();

@teo-tsirpanis
Copy link
Contributor

@DoomerDGR8 it has been renamed to [GeneratedRegex].

@danmoseley
Copy link
Member

I think our mechanism for noting significant preview->preview breaking changes is to put in the issues like #7716 and then feed into the release blog. I think we maybe missed that issue this time - but it wasn't in there anyway. I added it now. So hopefully it is found.

@amis92
Copy link

amis92 commented Sep 16, 2022

Hi, not sure where to raise that, but it seems the https://dotnetcli.azureedge.net/dotnet/Sdk/7.0/latest.version doesn't work correctly (it refers to Preview 7 still), which causes these two invocations to have different results:

> .\dotnet-install.ps1 -Channel 7.0 -Quality preview -DryRun
[snipped for brevity]
dotnet-install: Payload URLs:
dotnet-install: URL #0 - aka.ms: https://dotnetcli.azureedge.net/dotnet/Sdk/7.0.100-rc.1.22431.12/dotnet-sdk-7.0.100-rc.1.22431.12-win-x64.zip

> .\dotnet-install.ps1 -Channel 7.0 -DryRun
[snipped for brevity]
dotnet-install: Payload URLs:
dotnet-install: URL #0 - primary: https://dotnetcli.azureedge.net/dotnet/Sdk/7.0.100-preview.7.22377.5/dotnet-sdk-7.0.100-preview.7.22377.5-win-x64.zip
dotnet-install: URL #1 - legacy: https://dotnetcli.azureedge.net/dotnet/Sdk/7.0.100-preview.7.22377.5/dotnet-dev-win-x64.7.0.100-preview.7.22377.5.zip

Which in the end will install Preview 7 for dotnet-install -Channel 7.0 and RC1 for dotnet-install -Channel 7.0 -Quality preview.

It's important for CI/CD scenarios where we want to start using .NET 7 with Release Candidates and then fluently move to GA when it's released (so we want to just use the dotnet-install -Channel 7.0 command).

@dcwhittaker
Copy link
Member Author

@amis92 I've just checked all of them and updated the SDK version. If you could try again and let me know if you're still running into issues. Thanks so much!

@amis92
Copy link

amis92 commented Sep 16, 2022

I guess I'll need to wait a bit for CDN to refresh cache, as ./dotnet-install.ps1 -Channel 7.0 -DryRun -NoCdn now does resolve to RC1, but same without -NoCdn switch still has Preview 7. Thanks!

@amis92
Copy link

amis92 commented Sep 19, 2022

Hmm @dcwhittaker I'm not sure how long it's going to get cached? https://dotnetcli.azureedge.net/dotnet/Sdk/7.0/latest.version (which is what ./dotnet-install.ps1 -Channel 7.0 -DryRun uses afaik) is still cached on the edge if I understand correctly and returns Preview 7. Shouldn't these files have cache purged for them when updating?

@dcwhittaker
Copy link
Member Author

Hi @amis92 - can you try again? We just purged the cache again.

@amis92
Copy link

amis92 commented Sep 20, 2022

I've verified - that's all fixed now, thanks so much!

@Chamberlain91
Copy link

Using internal fixed float M[16]; for a Mat4 struct is not being initialized to all zeros in an Android release build.

@sub7ero
Copy link

sub7ero commented Sep 25, 2022

image

The code analysis breaks now. Unfortunatley no fix as described here works.

@esskar
Copy link

esskar commented Sep 29, 2022

New issue created #7840

@dcwhittaker dcwhittaker unpinned this issue Oct 11, 2022
@dcwhittaker
Copy link
Member Author

Closed in favor of #7865

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

8 participants