Skip to content

Rename host key to _EXPERIMENTAL namespace to prevent SDK task failures #46248

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

Merged

Conversation

baronfel
Copy link
Member

Due to VS testing of 9.0.200 finding several places in the SDK that were doing a combination of:

  • checking in MSBuild Targets if DOTNET_HOST_PATH was null and setting some backstop values, then
  • inside Task implementations reading the value of DOTNET_HOST_PATH from environment.

Because of this combination tasks would hard-error.

We're going to effectively unset this key by renaming it so that we can continue with progress on dotnet/msbuild#11142 while not impacting Tasks that need to be unified in their detection logic.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Request triage from a team member labels Jan 23, 2025
@baronfel baronfel changed the title Rename host key to _EXPERIMENTAL suffix to prevent SDK task failures Rename host key to _EXPERIMENTAL namespace to prevent SDK task failures Jan 23, 2025
Copy link
Member

@joeloff joeloff left a comment

Choose a reason for hiding this comment

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

Long term we should maybe consider moving all the experimental properties into a separate class so we have them in a single place and people don't end up with typos

@baronfel
Copy link
Member Author

@joeloff long term I don't want to have any experimental properties :D I'd expect us to delete this by .NET 10 GA at the latest if all goes well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants