Home/ Questions/Q 8199019
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T06:05:10+00:00

One of our underlying projects is packaged via NuGet and distributed (internally) so that

  • 0

One of our underlying projects is packaged via NuGet and distributed (internally) so that other teams can consume the library – let’s call it “Core.” With NuGet 1.x, we got a reference in our .csproj file that looked something like this:

<Reference Include="Core">
    <SpecificVersion>False</SpecificVersion>
<HintPath>..\packages\Core.1.4.1.381\lib\net40\Core.dll</HintPath>

After upgrading to NuGet 2.0, this same reference looks like this:

<Reference Include="Core, Version=1.4.1.381, Culture=neutral, processorArchitecture=MSIL">
    <SpecificVersion>False</SpecificVersion>
<HintPath>..\packages\Core.1.4.1.381\lib\net40\Core.dll</HintPath>

In the Include attribute, does the Version matter? I’m explicitly setting SpecificVersion to false. I’ve looked through the MSBuild Project File Schema Reference, but it didn’t see anything regarding how this attribute is parsed.

Thanks for input on this.

-SethO

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I tried under VS2010,
    if you specify :

    <SpecificVersion>False</SpecificVersion>

    the version under <Reference></Reference> is ignored.

    • 0