So LinqBridge is tagged as:

LinqBridge (1.3.0) - >= net20 < net35

but it's still installed for .NET 4.x?

Yes, all the packages are on nuget.org.

So LinqBridge is tagged as:
LinqBridge (1.3.0) - >= net20 < net35
but it's still installed for .NET 4.x?

Yes, this is the problem.

I tried with:

source https://nuget.org/api/v2

nuget HtmlAgilityPack = 1.4.6
nuget Fizzler.Systems.HtmlAgilityPack

and it gives me:

<Choose>
  <When Condition="$(TargetFrameworkIdentifier) == '.NETFramework' And ($(TargetFrameworkVersion) == 'v2.0' Or $(TargetFrameworkVersion) == 'v3.0')">
    <ItemGroup>
      <Reference Include="LinqBridge">
        <HintPath>..\..\packages\LinqBridge\lib\net20\LinqBridge.dll</HintPath>
        <Private>True</Private>
        <Paket>True</Paket>
      </Reference>
    </ItemGroup>
  </When>
</Choose>

Maybe something else is making trouble.

Add Fizzler package into the mix.

Will try. But probably tomorrow.
On Dec 30, 2014 3:12 PM, "Vasily Kirichenko" [email protected]
wrote:

Add Fizzler package into the mix.

—
Reply to this email directly or view it on GitHub
#486 (comment).

Thanks!

I've create a minimal repro: https://github.com/vasily-kirichenko/PacketTest

I minimized it even more :)

I just run paket update:

that's weird. Everything looks good.

ok paket install gives a different result. I can reproduce.

I think I understand the issue - will try to fix tomorrow. Thanks for reporting.

Yes, I've got the same result at home machine :( Will retest on the machine at work in a minute.

I've caught it :) Pull the changes from my repo - I removed everything from paket.references, so the project file is clean. Now add

HtmlAgilityPack
Fizzler.Systems.HtmlAgilityPack

into it, then run paket install and the bug will appear (LinqBridge.dll will be referenced).

Thanks!

Yep. It's a bug in "install" - "paket update" seems ok.

"install" has to parse/keep the dependency restrictions.
"update" is not affected since it computes everything from scratch.

Please retry.

0.20.3, paket install

 <Choose>
    <When Condition="($(TargetFrameworkIdentifier) == '.NETFramework' And ($(TargetFrameworkVersion) == 'v2.0' Or $(TargetFrameworkVersion) == 'v3.0' Or $(TargetFrameworkVersion) == 'v3.5' Or $(TargetFrameworkVersion) == 'v4.0' Or $(TargetFrameworkVersion) == 'v4.5' Or $(TargetFrameworkVersion) == 'v4.5.1' Or $(TargetFrameworkVersion) == 'v4.5.2' Or $(TargetFrameworkVersion) == 'v4.5.3')) Or ($(TargetFrameworkIdentifier) == 'MonoAndroid') Or ($(TargetFrameworkIdentifier) == 'MonoTouch')">
      <ItemGroup>
        <Reference Include="LinqBridge">
          <HintPath>packages\LinqBridge\lib\net20\LinqBridge.dll</HintPath>
          <Private>True</Private>
          <Paket>True</Paket>
        </Reference>
      </ItemGroup>
    </When>
  </Choose>
 </Project>

(did you run update before? the new install assumes the lockfile is in "correct" state and shouldn't break it. But it doesn't fix broken lockfiles)

will try to run with your latest repro. Did my test on the thingy from yesterday.

Ok I tried with your latest repro:

Please run paket update once. This will fix the broken lockfile (broken due to bug in earlier paket install)

Subsequent runs of paket install will respect the targetframework restrictions.

1. delete paket.lock
2. remove everything from paket.references
3. run paket install
4. All refs are removed from project file
5. Revert paket.references back
6. run paket install
7. the project file is correctly modified

I think it should check if project file contains correct when Conditions and modifies them if needed.

^^ that's basically what paket update does.

OK :) Thanks.

I think it should check if project file contains correct when Conditions and modifies them if needed.

that's what we do. The issue was, that the lockfile didn't containt the framework restrictions.