Fix duplicate PackageReferences for MSTest packages during project conversion #318
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.
Problem
When converting legacy project files that already contain MSTest packages (
MSTest.TestAdapter
andMSTest.TestFramework
), the transformation was creating duplicate PackageReferences. This happened because the transformation only checked for the existence ofMicrosoft.NET.Test.Sdk
before adding all test packages, but didn't check if individual MSTest packages already existed.Example of the Issue
Before the fix, a project with:
Would end up with duplicates after conversion:
Solution
Modified
TestProjectPackageReferenceTransformation
to:Microsoft.NET.Test.Sdk
already existsChanges Made
existingPackageReferences.Any(existingRef => existingRef.Id == testRef.Id)
Microsoft.NET.Test.Sdk
continue to work as beforeTest Coverage
Added comprehensive test cases covering:
Fixes #317.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.