Skip to content

Use SdkResolver APIs for reporting environment variables #49866

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

Open
wants to merge 4 commits into
base: darc-main-7628065e-94f2-4f11-a6d5-3ab587167c53
Choose a base branch
from

Conversation

baronfel
Copy link
Member

@baronfel baronfel commented Jul 19, 2025

Requires the MSBuild API changes from #49740. This PR is targeting main only because our pipelines aren't set up to allow PR runs for branches/PRs that are themselves branched off off of darc-codeflow branches.

This uses the proper APIs for reporting env variables, but because it requires a newer version of the MSBuild APIs and those APIs have brought increased dependency bumps we probably need to take a deeper look at the coordination involved here.

Comment on lines -136 to +145
<MicrosoftBclAsyncInterfacesToolsetPackageVersion>8.0.0</MicrosoftBclAsyncInterfacesToolsetPackageVersion>
<MicrosoftBclAsyncInterfacesToolsetPackageVersion>9.0.0</MicrosoftBclAsyncInterfacesToolsetPackageVersion>
<MicrosoftDeploymentDotNetReleasesToolsetPackageVersion>2.0.0-preview.1.24427.4</MicrosoftDeploymentDotNetReleasesToolsetPackageVersion>
<SystemBuffersToolsetPackageVersion>4.5.1</SystemBuffersToolsetPackageVersion>
<SystemCollectionsImmutableToolsetPackageVersion>8.0.0</SystemCollectionsImmutableToolsetPackageVersion>
<SystemCollectionsImmutableToolsetPackageVersion>9.0.0</SystemCollectionsImmutableToolsetPackageVersion>
<SystemMemoryToolsetPackageVersion>4.5.5</SystemMemoryToolsetPackageVersion>
<SystemReflectionMetadataLoadContextToolsetPackageVersion>8.0.0</SystemReflectionMetadataLoadContextToolsetPackageVersion>
<SystemReflectionMetadataToolsetPackageVersion>8.0.0</SystemReflectionMetadataToolsetPackageVersion>
<SystemTextJsonToolsetPackageVersion>8.0.5</SystemTextJsonToolsetPackageVersion>
<SystemReflectionMetadataLoadContextToolsetPackageVersion>9.0.0</SystemReflectionMetadataLoadContextToolsetPackageVersion>
<SystemReflectionMetadataToolsetPackageVersion>9.0.0</SystemReflectionMetadataToolsetPackageVersion>
<SystemTextJsonToolsetPackageVersion>9.0.0</SystemTextJsonToolsetPackageVersion>
<SystemThreadingTasksExtensionsToolsetPackageVersion>4.5.4</SystemThreadingTasksExtensionsToolsetPackageVersion>
<SystemResourcesExtensionsToolsetPackageVersion>8.0.0</SystemResourcesExtensionsToolsetPackageVersion>
<SystemResourcesExtensionsToolsetPackageVersion>9.0.0</SystemResourcesExtensionsToolsetPackageVersion>
Copy link
Member Author

Choose a reason for hiding this comment

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

All of this is the scary stuff @rainersigwald @YuliiaKovalova @marcpopMSFT @jaredpar

How do we usually navigate/negotiate bumps to these shared dependencies between MSBuild/Roslyn/SDK/VS?

@baronfel baronfel marked this pull request as ready for review July 19, 2025 16:24
@baronfel baronfel changed the base branch from darc-main-7628065e-94f2-4f11-a6d5-3ab587167c53 to main July 19, 2025 16:25
@baronfel baronfel requested review from a team and tmat as code owners July 19, 2025 16:25
@joeloff
Copy link
Member

joeloff commented Jul 19, 2025

Where are the actual changes? This seems to mostly be SC.L related.

@baronfel
Copy link
Member Author

baronfel commented Jul 19, 2025

@joeloff the two last commits are the actual change - the rest of the commits are

  • VMR codeflow to bring in the MSBuild dep bumps I need
  • because our CI pipelines don't run when you do a branch targeting a VMR codeflow branch

So really just check out b498344 and 3ab8cb9.

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.

2 participants