Skip to content

Conversation

@jonathanpeppers
Copy link
Member

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!

Copy link
Member

@radekdoulik radekdoulik left a 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]

@radekdoulik
Copy link
Member

dotnet/java-interop#782 should fix it

@radekdoulik
Copy link
Member

There's also problem with illink and --dump-dependencies. The log is missing for some reason, but locally I get this:

ILLink : error IL1015: Unrecognized command-line option: '--dump-dependencies

I will take a look at it.

@jonathanpeppers jonathanpeppers force-pushed the net6.0.100-alpha.1.21064.27 branch from 0924425 to 71ffedc Compare January 18, 2021 19:19
jonathanpeppers and others added 2 commits January 19, 2021 14:15
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 jonathanpeppers force-pushed the net6.0.100-alpha.1.21064.27 branch from 71ffedc to f32447d Compare January 19, 2021 20:15
@dotnet dotnet deleted a comment from azure-pipelines bot Jan 19, 2021
@jonathanpeppers jonathanpeppers marked this pull request as ready for review January 19, 2021 22:19
@jonathanpeppers
Copy link
Member Author

The failure on the BCL Emulator Tests will hopefully be fixed by: #5525

@jonpryor jonpryor merged commit 7cf4105 into dotnet:master Jan 21, 2021
<!-- 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>
Copy link
Member Author

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.

Copy link
Member

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: dotnet/macios#10501

Copy link
Member Author

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... 😞

@jonathanpeppers jonathanpeppers deleted the net6.0.100-alpha.1.21064.27 branch January 21, 2021 20:05
@github-actions github-actions bot locked and limited conversation to collaborators Jan 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants