Bump to .NET 6.0.100-alpha.1.21064.27 #5504
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
radekdoulik
reviewed
Jan 15, 2021
There was a problem hiding this comment.
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. |
jonathanpeppers
force-pushed
the
net6.0.100-alpha.1.21064.27
branch
from
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
jonathanpeppers
force-pushed
the
net6.0.100-alpha.1.21064.27
branch
from
71ffedc
to
f32447d
Compare
|
The failure on the BCL Emulator Tests will hopefully be fixed by: #5525 |
jonathanpeppers
commented
Jan 21, 2021
| @@ -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.
/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.
Ok, we're bumping to the same version: xamarin/xamarin-macios#10501
There was a problem hiding this comment.
We still don't have builds this morning, CI issues... 😞
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes: dotnet/installer@efac3f2...47153b5
We are hitting a problem inside Visual Studio, where our .NET 6
projects aren't able to build:
dotnet buildworked 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!