Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork340
Fix dotnet test Command Not Recognizing NUnit3TestAdapter#164
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Fix dotnet test Command Not Recognizing NUnit3TestAdapter#164
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Move reference to NUnit3TestAdapter to ItemGroup without TargetFramework condition
FreeAndNil commentedAug 3, 2024
@mobilebilly Thank you very much for your contribution. |
…it3TestAdapter version to 4.5.0
mobilebilly commentedAug 4, 2024
@FreeAndNil , no problem. |
FreeAndNil left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Please adjust as proposed, then we can merge.
Uh oh!
There was an error while loading.Please reload this page.
Set IsTestProject to true and clean up garbage from old project file.
mobilebilly commentedAug 5, 2024
@FreeAndNil, the additional change in the test project is done. thank you |
FreeAndNil left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thanks a lot.
60d4fbc intoapache:Feature/111-Dropping-support-for-older-runtimes
Fix for Issue#109
This fix addresses the issue where the dotnet test command cannot recognize the NUnit3TestAdapter in existing ItemGroup elements.
Changes Made:
Moved the reference to NUnit3TestAdapter to an ItemGroup without a TargetFramework condition.