Repository navigation
Unexpected empty.nupkg in output directory #1714
Description
Describe the bug
Verify.MSTest version 31.15.0 adds an empty.nupkg file in the output directory of our unit test projects.
The problem is that this file is being picked up by our CICD to be pushed to a NuGet registry.
Is there a way to avoid that the "EmptyFiles" directory is being created?
Activity
gsolic commentedon Apr 22, 2026
We also have the same issue with version
31.16.1.SimonCropp commentedon Apr 23, 2026
@gsolic can u provide a zipped solution that reproduces the problem.
gsolic commentedon Apr 23, 2026
You can use the
NUnitNugetUsageproject as a reference. From the repository root, run:After execution, you will notice that the file
.\usages\NUnitNugetUsage\bin\Release\net10.0\EmptyFiles\archive\empty.nupkgis generated and subsequently picked up by our CI pipeline.My question is: what is the purpose of the
EmptyFilesdirectory in the output, and is there a way to prevent it from being created?SimonCropp commentedon Apr 24, 2026
can u try 31.16.2
gsolic commentedon Apr 24, 2026
EmptyFilesis still in the output directory on 31.16.2 with dotnet 10.0.107SimonCropp commentedon Apr 24, 2026
did u manually delete your bin and obj directories?
gsolic commentedon Apr 24, 2026
yes, i did
SimonCropp commentedon Apr 24, 2026
in that case i need a minimal repro since the the nunit usage no longer reproduces it
gsolic commentedon Apr 24, 2026
It turns out this was my mistake. I checked out the
31.16.2tag and ran theNUnitNugetUsagetest, but only just realized that in this tag theNUnitNugetUsage.csprojstill references31.16.1. I had assumed it was using a direct project reference instead.Sorry for the confusion. It looks like
31.16.2no longer produces theEmptyFilesissue. Thanks for your help!SimonCropp commentedon Apr 24, 2026
@gsolic good to hear
Bump Verify.XunitV3 from 31.15.0 to 31.16.3 (#326)