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

Don't ngen Microsoft.IO.Redist for VS #11256

Merged
merged 1 commit into from
Jan 20, 2025
Merged

Conversation

rainersigwald
Copy link
Member

@rainersigwald rainersigwald commented Jan 10, 2025

IO.Redist is a core part of VS now, so we shouldn't ngen it for the VS context--best case that's redundant work, worst case if we mismatch versions it might cause further confusion.

Internal PR: https://dev.azure.com/devdiv/DevDiv/_git/VS/pullrequest/602240

Validate:

  • No MethodsJitted regressions
  • This ngen call goes away.

IO.Redist is a core part of VS now, so we shouldn't ngen it for
the VS context--best case that's redundant work, worst case if we
mismatch versions it might cause futher confusion.
Copy link
Contributor

Hello @rainersigwald, I noticed that you’re changing an .swr file or any file under src/Package/MSBuild.VSSetup.. Please make sure to validate this change by an experimental VS insertion. This is accomplished by pushing to an exp/* branch, which requires write permissions to this repo.

@rainersigwald rainersigwald self-assigned this Jan 13, 2025
@rainersigwald rainersigwald marked this pull request as ready for review January 14, 2025 21:09
@rainersigwald rainersigwald enabled auto-merge (squash) January 16, 2025 14:56
@rainersigwald rainersigwald merged commit ca511e0 into main Jan 20, 2025
10 checks passed
@rainersigwald rainersigwald deleted the exp/no-ngen-io-redist-in-vsn branch January 20, 2025 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants