- my build script is creating a package and dropping it at \\mycompany\repo
- one day, build failed and the package dropped in \\mycompany\repo is of zero bytes
- Now in VS team has \\ mycompany\repo as package source
- launching package manage dialog, Online or update tab shows the following error
unable to read package from myprojectsolution220.127.116.11.nupkg
It should just ignore the zero byte nupkg file, otherwise all devs in my team cannot access the repo until someone finds it's caused by zero byte package & is deleted or build is successful.