Ok this is a new fucked up situation. RavenDB.Client nuspec says

<frameworkAssemblies>
  <frameworkAssembly assemblyName="System.ComponentModel.Composition" targetFramework=".NETFramework4.0" />
</frameworkAssemblies>

So we think it's only for net4.

we need a way to.keep these

we could introduce a Paket-keep flag, but this would mean manually editing of csproj file

we could also add a syntax to the references file. Like

frameworkAssembly System.ComponentModel.Composition

Why does paket remove the references?

The original idea is to remove duplicates.
The nuspec in question requires the assembly framework reference. So we add
it. Then you have two references. Which is also a bug.

But your question hints to a better strategy. Maybe we should not
remove/replace existing references. Instead we could just update our model.

This may actually work and solve another problem. Sometimes the easy
solutions are hard to see.
On Nov 21, 2014 3:39 PM, "Jon Canning" [email protected] wrote:

Why does paket remove the references?

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

My local version seems to handle this case now. Will need to make it more robust.

It would be cool if you could test 0.16 alpha version if it works for you.

Looks good!

Just paket'd (and FAKE'd!) another more complicated project that was losing numerous references. All good now.