NuGet package install and assembly version in csproj files

[vphad]

Hi Team, We are using NuGet in our projects, we are facing issues with the csproj references of the NuGet packages.

Scenario 1 When we are installing few packages to the solution on Dev system with below details,

• Windows 7, x64 bit
• Visual Studio 2012
• NuGet 2.8
• PTC Integrity for version control

It adds the specific version to the csproj files. as given below, (csproj snippet),

`

..\packages\ABCD.XYZ.2.0.0.0\lib\net45\ABCD.XYZ.dll True

`

Scenario 2 When adding the same package on build server with below details

• Windows Server 2008 R2
• Visual Studio 2012
• NuGet 2.8
• PTC Integrity for version control

It adds below details,

`

..\packages\ABCD.XYZ.2.0.0.0\lib\net45\ABCD.XYZ.dll

  <Private>True</Private>
</Reference>

`

How is the specific version is added ? On stackoverflow, I see post is mentioning that it adds below tag to the csproj for that user, but that's not the case for us.

<SpecificVersion>False</SpecificVersion>

• My scenario here is that, our build increments the ABCD.XYZ Assembly Version with each build. Therefore the project which has above reference is failing as it's not able to find the version above (NuGet adds strong name in the reference)
• I have tried various build configurations like Debug, Release, x64, Any CPU etc.
• Updating csproj manually, isn't that flexible option

1. How is this specific version or strong name is added to the csproj ? 2. Is there any option to add/ignore specific version ? 3. What is required to add the reference as highlighted in Scenario 2 ?

Please let us know if additional data is required.

[vphad]

Can someone please look into this ? It's affecting our builds.

[sheitmann]

I have the same issue with a specific package. The hint path is always updated but the version in the include attribute is sometimes wrong. Not sure if it helps to identify the source for the issue but I have other packages that have this problematic package as dependency with an older version.

[prorok-kane]

Any updates about this issue?