Paket removes System.ComponentModel.Composition reference

[JonCanning]

I'm using Paket to install RavenDB.Client, and a call to:

Raven.Client.Indexes.IndexCreation.CreateIndexes

in my code requires that System.ComponentModel.Composition is manually referenced. However, whenever I run paket update the reference is removed

Create an empty library and replace the class that's created with this

type Class1() = 
  member this.X = Raven.Client.Indexes.IndexCreation.CreateIndexes(System.Reflection.Assembly.GetExecutingAssembly(), null)

and reference System.ComponentModel.Composition

You may have to paket update a couple of times to see the problem

[forki]

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

[forki]

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

[forki]

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

frameworkAssembly System.ComponentModel.Composition

[JonCanning]

Why does paket remove the references?

[forki]

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" notifications@github.com wrote:

Why does paket remove the references?

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

[forki]

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

[forki]

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

[JonCanning]

Looks good!

[JonCanning]

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