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

Update to .NET 10 SDK and TFM to net10.0 in arcade #15221

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

ViktorHofer
Copy link
Member

To double check:

@@ -3,7 +3,7 @@

<PropertyGroup>
<IncludeDotNetCli Condition=" '$(IncludeDotNetCli)' != 'true' ">false</IncludeDotNetCli>
<AspNetCoreRuntimeVersion>9.0.0-rc.2.24474.3</AspNetCoreRuntimeVersion>
<AspNetCoreRuntimeVersion>10.0.0-alpha.2.24531.4</AspNetCoreRuntimeVersion>
Copy link
Member

@am11 am11 Nov 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it was unintentional that aspnetcore missed alpha 1. First net10.0 branding PR was merged dotnet/aspnetcore#57340 then few hours later on the same day, release/9.0 -> main sync bumped the prerelease dotnet/aspnetcore#57434 version.

cc @wtgodbe arcade has one failing test to keep the prerelease levels same, which is how this was detected. I think it's functionally not a problem, just a branding glitch.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching that - opened dotnet/aspnetcore#58884

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, would it be alright to disable the test for now? If we switch back to alpha1, anybody restoring with floating versions will get the last alpha2 package instead of the latest alpha1 package, until we switch to preview1

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be, or perhaps we can bump dotnet/sdk to alpha.2. @ViktorHofer's call. 🙂

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spoke with Viktor offline about this, let's keep the branding as-is & disable the test for now

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll switch to preview.1 in not too long, so leaving as alpha.2 is fine by me.

@ViktorHofer
Copy link
Member Author

@mmitche what do you think, should we start using a .NET 10 SDK in our repos? I would probably update to a slightly newer one before merging but it already includes the net10.0 TFM, templates and other changes that are needed.

@@ -16,6 +16,11 @@
<RepositoryUrl>https://github.com/dotnet/arcade</RepositoryUrl>
<!-- Only upgrade NuGetAudit warnings to errors for official builds. -->
<WarningsNotAsErrors Condition="'$(OfficialBuild)' != 'true'">$(WarningsNotAsErrors);NU1901;NU1902;NU1903;NU1904</WarningsNotAsErrors>
<!-- TODO: Remove when Arcade SDK updated TargetFrameworkDefaults.props for .NET 10. -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<!-- TODO: Remove when Arcade SDK updated TargetFrameworkDefaults.props for .NET 10. -->
<!-- TODO: Remove when arcade updates to a new Arcade SDK with matching TargetFrameworkDefaults.props -->

@@ -1,10 +1,10 @@
{
"sdk": {
"version": "9.0.100",
"version": "10.0.100-alpha.1.24551.9",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, I would update to a newer SDK, but it probalby doesn't make too much difference.

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.

4 participants