Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Paket removes references which are under user control

See original GitHub issue

Description

References which are under user control should not be removed by Paket. Paket removes always references and let our build fail

Repro steps

We have a silverlight class library project which we use for testing. We add e.g. System.Net to that library and want to use that in our code. When we add the nuget dependency Microsoft.Bcl.Async then System.Net is removed because the for net40 this is specified as reference.

Expected behavior

We should be able to have control over that reference. But Paket always removes references. Also specifying <Paket>False</Paket> does not help.

Actual behavior

We always lose the references after a paket run.

Known workarounds

none. Use paket 2 as this behaviour seems new in Paket 3.

Related information

N/A

Issue Analytics

State:
Created 7 years ago
Comments:17 (17 by maintainers)

Top GitHub Comments

1reaction

forkicommented, Jun 22, 2016

it’s what the package specifies. Anyways. a fix is underway that allows you to add paket = false

0reactions

Stiftcommented, Jun 22, 2016

ok. thx.

Top Results From Across the Web

PackageReference in project files - NuGet

Package references, using <PackageReference> MSBuild items, specify NuGet package ... into your project file, then remove packages.config.

FAQ — Frequently Asked Questions

Each project will have a paket.references file that specifies which of the dependencies are installed in the project. Each of these files should...

The paket.dependencies file

Paket usually adds all direct and transitive dependencies that are listed in paket.references files to project files next to the respective paket.references ......

Paket error: "Package was referenced, but it was not found ...

Option 1. The easiest way to fix this error is to delete the file paket.lock , and force Paket to regenerate this file...

Getting Started with Paket – Part 1 - The Cockney Coder

Firstly, it modifies csproj files so they're in sync with paket.references files (when you add or remove a dependency to a project).