Skip to content
This repository was archived by the owner on Nov 6, 2024. It is now read-only.

Bump to xamarin/xamarin-android/release/6.0.1xx-preview10@27295e27 - #535

Merged
Jonathan Pobst (jpobst) merged 1 commit into
mainfrom
fix-ji
Nov 2, 2021
Merged

Jonathan Pobst (jpobst) merged 1 commit into
mainfrom
fix-ji

Conversation

@jpobst

@jpobst Jonathan Pobst (jpobst) commented Nov 1, 2021 •

Copy link
Copy Markdown
Contributor

Copied from: dotnet/android-libraries#413
Context: https://github.com/xamarin/xamarin-android/commits/release/6.0.1xx-preview10
Context: https://github.com/dotnet/maui/wiki/Installing-.NET-6

We need to build with a version of the .NET 6 android workload that
contains the fix:

dotnet/java-interop@2d5431f

For .NET 6, we should:

  1. Install the latest public .NET 6 RC 2 release.
  2. Use a workload.json file to pin to a specific build of the
    android workload.
  3. Use the dotnet6 feed when installing the workload.

I used the workload.json file currently reported by running:

dotnet workload update --print-rollback

I adjusted the version number to match the appropriate build of:

"microsoft.net.sdk.android": "31.0.101-preview.10.56",

@jpobst

Copy link
Copy Markdown
Contributor Author

Spot check looks good:

image

Comment thread azure-pipelines.yaml
version: $(DotNetVersion)
- pwsh: |
dotnet workload install android
dotnet workload update --verbosity diag --from-rollback-file workload.json --source $(Dotnet6Source) --source $(NuGetOrgSource)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

so this is trick to "pin" versions for workloads?

workload.json is default name or can it be something else?

@moljac moljac (moljac) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

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.

2 participants