Nuget Package always one step behind

See attached screen shot.

But basically I always need to do 2 builds to get a change to deploy as the build is always using a package from the last build.
I have the same problem in 2 different projects however a 3rd project does not have this issue.


Can you share more details around how you are creating the release? Is it via our TeamCity plugin? If so you’ll need a seperate, dependent build configuration since TeamCity doesn’t publish the package until after a build configuration completes. We have more details here: