c# - Nuget creates specificly versioned references to assemblies in projects -

my team experiencing issue when using nuget package management creates references in project specific versions of dll. there way stop nuget creating these tightly coupled references?

a bit of background.

we using nuget manage our internal shared libraries. packages installed using vs ui. nuget packages created using nuget.exe spec , nuget.exe pack on .csproj file.

we use standard branching strategy of mainline dev done on trunk , release off rc branch.

we didn't want enter versioning hell naming of our packages x.y.z-build123 because dev may need local build away our ci system , use test downstream solutions. our answer simplify our package versioning saying trunk builds x.y.z-staging , rc build named x.y.z enable dev local build , of nuget.exe install pointing repository on dev's machine use build in downstream solutions. without having update packages etc.

the problem seeing while works fine @ package level. builds failing references in projects specific file versions of assembly. on local dev build not include build number on ci server will.

ie.

a project has reference following.

the build number part of version (123) different on ci server local dev machine 0.

is there way nuget create version agnostic references eg assembly name rather strong name.

it appears have found solution this.

i created new console project in attempt recreate issue. added package using , added without version information!

i not see odd settings on previous project started messing around. able recreate issue following steps. 1) add nuget package project 2) build 3) uninstall nuget package 4) reinstall nuget package

this 4th step makes package install project version information.

what boils down to, if have assemblies in bin folder , attempt add (or uninstall , reinstall) new references added project version information.

the solution make sure clean solution before dealing nuget.