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
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.Asyncthen 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