Skip to content

AOT compatible: NuGet.DependencyResolver.Core#7138

Merged
Nigusu-Allehu merged 1 commit intodevfrom
dev-nyenework-AOT-N.D.C
Feb 17, 2026
Merged

AOT compatible: NuGet.DependencyResolver.Core#7138
Nigusu-Allehu merged 1 commit intodevfrom
dev-nyenework-AOT-N.D.C

Conversation

@Nigusu-Allehu
Copy link
Copy Markdown
Member

@Nigusu-Allehu Nigusu-Allehu commented Feb 14, 2026

Bug

Fixes:

Related: NuGet/Home#14408

Description

Add IsAotCompatible property and fix any AOT analysis warnings. This is part of a broader effort to make
NuGet's libraries compatible with Native AOT

PR Checklist

  • Meaningful title, helpful description and a linked NuGet/Home issue
  • Added tests
  • Link to an issue or pull request to update docs if this PR changes settings, environment variables, new feature, etc.

@Nigusu-Allehu Nigusu-Allehu self-assigned this Feb 14, 2026
@Nigusu-Allehu Nigusu-Allehu marked this pull request as ready for review February 15, 2026 23:04
@Nigusu-Allehu Nigusu-Allehu requested a review from a team as a code owner February 15, 2026 23:04
@Nigusu-Allehu Nigusu-Allehu enabled auto-merge (squash) February 15, 2026 23:04
Copy link
Copy Markdown
Member

@zivkan zivkan left a comment

Choose a reason for hiding this comment

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

Is there a reason you created one PR per project?

If it was to see which ones build and which ones don't, you could have gotten quicker feedback by building locally. This property only enables analyzers, it doesn't change runtime.

@Nigusu-Allehu
Copy link
Copy Markdown
Member Author

Is there a reason you created one PR per project?

If it was to see which ones build and which ones don't, you could have gotten quicker feedback by building locally. This property only enables analyzers, it doesn't change runtime.

That makes sense. In the previous PR #7097, we ran into an analyzer error that only reproduced on Linux, which influenced how I approached it. That said, I could have grouped the changes into a single PR as well. There wasn’t a strong technical reason for splitting them. at the time, I just chose to go project by project.

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