Skip to content
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

Update MSBuild.exe to set interactive for interactive user sessions #46422

Open
baronfel opened this issue Jan 30, 2025 · 3 comments
Open

Update MSBuild.exe to set interactive for interactive user sessions #46422

baronfel opened this issue Jan 30, 2025 · 3 comments
Assignees
Labels
Area-NetSDK untriaged Request triage from a team member

Comments

@baronfel
Copy link
Member

No description provided.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-NetSDK untriaged Request triage from a team member labels Jan 30, 2025
@rainersigwald
Copy link
Member

Concerns to look out for:

  • It's kinda hard to detect interactive user sessions in a bulletproof way
  • We really, really don't want to accidentally set --interactive for CI/PR/remote/server builds, because that manifests as "hard-to-diagnose build hang".

@baronfel
Copy link
Member Author

Agree. Critical to all of this is the ability for a user to force the interactive-ed-ness to off, which can always be done by explicitly specifying /interactive:false or equivalent.

@KalleOlaviNiemitalo
Copy link
Contributor

KalleOlaviNiemitalo commented Jan 31, 2025

/interactive:false can be difficult to add when MSBuild is only invoked by a third-party NPM package as part of a larger node.js build. Is there an environment variable to force noninteractive?

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

No branches or pull requests

3 participants