NGen Entity.Design and Data.Tools.Design.XmlCore (priority 3)#94
Draft
davkean wants to merge 1 commit into
Draft
NGen Entity.Design and Data.Tools.Design.XmlCore (priority 3)#94davkean wants to merge 1 commit into
davkean wants to merge 1 commit into
Conversation
…ls.Design.XmlCore (priority 3) Cowritten with Copilot
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Microsoft.Data.Entity.Design and Microsoft.VisualStudio.Data.Tools.Design.XmlCore load JIT-only today with no native image. NGEN both at priority 3 so the EF6 / EDMX designer pays no JIT cost when it first opens.
Both already ship to Common7\IDE (the app base), so they bind by name in the default load context and use the native image — no binding path, no LoadFrom.
Follows the same NGEN pattern used in VS repo PR 741831.
Cowritten with Copilot