-
Notifications
You must be signed in to change notification settings - Fork 528
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
Bump to .NET 6.0.100-alpha.1.21064.27 #5504
Bump to .NET 6.0.100-alpha.1.21064.27 #5504
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the compiler is more strict now:
/Users/runner/work/1/s/external/Java.Interop/src/Java.Interop/Java.Interop/JniNativeMethodRegistrationArguments.cs(10,26): error CA1802: Field 'invalidStateMessage' is declared as 'readonly' but is initialized with a constant value. Mark this field as 'const' instead. [/Users/runner/work/1/s/external/Java.Interop/src/Java.Interop/Java.Interop.csproj] [/Users/runner/work/1/s/tests/Mono.Android-Tests/Runtime-Microsoft.Android.Sdk/Mono.Android.NET-Tests.csproj]
dotnet/java-interop#782 should fix it |
There's also problem with illink and
I will take a look at it. |
0924425
to
71ffedc
Compare
Changes: dotnet/installer@efac3f2...47153b5 We are hitting a problem inside Visual Studio, where our .NET 6 projects aren't able to build: NETSDK1147: The following workload packs were not installed: Microsoft.Android.Sdk `dotnet build` worked fine, but not inside the IDE. Updating .NET 6 solved this issue. We haven't updated our build of .NET 6 since ~Nov 13, let's update!
To work around possible ILLink bug. With the original ordering we started getting: ILLink : error IL1015: Unrecognized command-line option: '--dump-dependencies
71ffedc
to
f32447d
Compare
The failure on the BCL Emulator Tests will hopefully be fixed by: #5525 |
@@ -72,7 +72,7 @@ | |||
<DotNetPreviewTool Condition=" '$(DotNetPreviewTool)' == '' ">$(DotNetPreviewPath)dotnet</DotNetPreviewTool> | |||
<!-- Version number from: https://github.com/dotnet/installer#installers-and-binaries --> | |||
<DotNetPreviewVersionBand Condition=" '$(DotNetPreviewVersionBand)' == '' ">6.0.100</DotNetPreviewVersionBand> | |||
<DotNetPreviewVersionFull Condition=" '$(DotNetPreviewVersionFull)' == '' ">$(DotNetPreviewVersionBand)-alpha.1.20562.2</DotNetPreviewVersionFull> | |||
<DotNetPreviewVersionFull Condition=" '$(DotNetPreviewVersionFull)' == '' ">$(DotNetPreviewVersionBand)-alpha.1.21064.27</DotNetPreviewVersionFull> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/cc @rolfbjarne this is the version of .NET 6 we bumped to.
I'll try updating net6-samples once the current build is complete.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, we're bumping to the same version: xamarin/xamarin-macios#10501
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still don't have builds this morning, CI issues... 😞
Changes: dotnet/installer@efac3f2...47153b5
We are hitting a problem inside Visual Studio, where our .NET 6
projects aren't able to build:
dotnet build
worked fine, but not inside the IDE. Updating .NET 6solved this issue.
We haven't updated our build of .NET 6 since ~Nov 13, let's update!