Skip to content

[release/6.0.4xx] Update dependencies from dotnet/msbuild#25507

Merged
v-wuzhai merged 6 commits intorelease/6.0.4xxfrom
darc-release/6.0.4xx-25fed7ac-59e6-49d9-8256-0c2cb5312529
May 30, 2022
Merged

[release/6.0.4xx] Update dependencies from dotnet/msbuild#25507
v-wuzhai merged 6 commits intorelease/6.0.4xxfrom
darc-release/6.0.4xx-25fed7ac-59e6-49d9-8256-0c2cb5312529

Conversation

@dotnet-maestro
Copy link
Copy Markdown
Contributor

@dotnet-maestro dotnet-maestro Bot commented May 18, 2022

This pull request updates the following dependencies

From https://github.com/dotnet/msbuild

  • Subscription: 0d1c02d6-f28b-4061-e94d-08da181a39e5
  • Build: 20220527.1
  • Date Produced: May 27, 2022 3:47:46 PM UTC
  • Commit: f1dae6ab690483458d37b8900f1d1e4a5fc72851
  • Branch: refs/heads/main

…0518.2

Microsoft.Build.Localization , Microsoft.Build
 From Version 17.3.0-preview-22266-03 -> To Version 17.3.0-preview-22268-02
@ghost ghost added the Area-CodeFlow label May 18, 2022
To match MSBuild's update from dotnet/msbuild#7629.

Also removed redundant version for
System.Security.Cryptography.ProtectedData that caused downgrades.
@rainersigwald rainersigwald force-pushed the darc-release/6.0.4xx-25fed7ac-59e6-49d9-8256-0c2cb5312529 branch from 0d6eca7 to bf38d57 Compare May 18, 2022 19:11
@dsplaisted
Copy link
Copy Markdown
Member

Same issue with System.Reflection.Metadata update as #25483.

@rainersigwald rainersigwald self-assigned this May 20, 2022
For .NET Framework task builds, use the SCI+SRM 5.0 instead of 6,
because 6 is not included in MSBuild 17.2 and lower's binding redirects.

On new MSBuild, everything gets binding redirected to 6.0.0.0 and is
fine. On older ones, the 1.x references from within HostModel get
redirected to 5.0, but the references within the task assembly itself
were 6.0 (because of references in this project). Both are loadable
side-by-side in the .NET Framework model, but they are incompatible
types.

Instead, compile this assembly against 5.0 versions, and apply the
manual binding redirect to 5.0 assemblies redistributed next to the task
assembly via `TaskWithAssemblyResolveHooks`.

Since the MSBuild packages now use 6.0, this requires some gymnastics:

1. explicitly reference the 6.0 packages in this project, so they can be
   annotated with `IncludeAssets="none"`.
2. download + explicitly reference the 5.0 packages _after_ RAR runs, to
   avoid the assembly-mismatch errors that RAR would generate.
3. explicitly copy SRM and SCI into the output folder.
@rainersigwald rainersigwald force-pushed the darc-release/6.0.4xx-25fed7ac-59e6-49d9-8256-0c2cb5312529 branch from 71b46ca to 66826cc Compare May 25, 2022 15:37
@rainersigwald
Copy link
Copy Markdown
Member

@dsplaisted Ok, I think my changes are ready for review. It's the best I could come up with to keep 6.0.400 working on MSBuild 17.2, but I'd love to not have to mess with things in this way. Ideas welcome!

After this is approved/redone, I'll port to main.

…0526.1

Microsoft.Build , Microsoft.Build.Localization
 From Version 17.3.0-preview-22266-03 -> To Version 17.3.0-preview-22276-01
@marcpopMSFT
Copy link
Copy Markdown
Member

I assume we'll need those changes in main as well.

dotnet-maestro Bot added 2 commits May 26, 2022 21:41
…0526.2

Microsoft.Build , Microsoft.Build.Localization
 From Version 17.3.0-preview-22266-03 -> To Version 17.3.0-preview-22276-02
…0527.1

Microsoft.Build , Microsoft.Build.Localization
 From Version 17.3.0-preview-22266-03 -> To Version 17.3.0-preview-22277-01
@v-wuzhai v-wuzhai merged commit a29c5ec into release/6.0.4xx May 30, 2022
@v-wuzhai v-wuzhai deleted the darc-release/6.0.4xx-25fed7ac-59e6-49d9-8256-0c2cb5312529 branch May 30, 2022 05:37
Comment on lines +77 to +78
<PackageDownload Include="System.Collections.Immutable" Version="[5.0.0]" GeneratePathProperty="true" />
<PackageDownload Include="System.Reflection.Metadata" Version="[5.0.0]" GeneratePathProperty="true" />
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks like you're not using the properties generated by GeneratePathProperty below. Was that intentional?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

IIRC it didn't actually produce the properties as I expected. In which case I probably should have removed the attributes here.

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