Skip to content

Use TargetFrameworkInformation.FrameworkName when determining the closest TFM for a project in lock file up to date checks#7223

Draft
nkolev92 wants to merge 1 commit intodevfrom
dev-nkolev92-lockFilesATF
Draft

Use TargetFrameworkInformation.FrameworkName when determining the closest TFM for a project in lock file up to date checks#7223
nkolev92 wants to merge 1 commit intodevfrom
dev-nkolev92-lockFilesATF

Conversation

@nkolev92
Copy link
Copy Markdown
Member

Bug

Fixes: NuGet/Home#12010

Description

Follow-up to #7218.

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.

@nkolev92 nkolev92 force-pushed the dev-nkolev92-lockFilesATF branch from cc649d4 to 8c88f76 Compare March 25, 2026 17:16
@nkolev92 nkolev92 changed the title GetReferenceNearest disambiguation Use TargetFrameworkInformation.FrameworkName when determining the matching TFM Mar 26, 2026
@nkolev92 nkolev92 changed the title Use TargetFrameworkInformation.FrameworkName when determining the matching TFM Use TargetFrameworkInformation.FrameworkName when determining the closest TFM for a project in lock file up to date checks Mar 26, 2026
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.

[Bug]: NU1004: The project Xxx has no compatible target framework for .NET vs .NET Framework cross reference with -LockedMode

1 participant