Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot install package - custom nodes #368

Closed
tpluscode opened this issue Nov 18, 2014 · 11 comments
Closed

Cannot install package - custom nodes #368

tpluscode opened this issue Nov 18, 2014 · 11 comments

Comments

@tpluscode
Copy link
Contributor

I'm using FluentAssertions. When I first converted from NuGet it got correctly added to the csproj.

However later reinstalls (unnecessary as in #366, but that's beside the point) fail to install that package. When I do paket add nuget FluentAssertions or update it says in yellow custom nodes for FluentAssertions => skipping.

What are these custom nodes and why can't the be ignored?

Adding --force didn't help. The package gets unpacked and is added to .dependencies but references aren't added.

@forki
Copy link
Member

forki commented Nov 18, 2014

can you please show us the csproj file?

@utopius
Copy link

utopius commented Nov 18, 2014

I'm having a similar problem where my project needs Castle.Windsor, but the only reference added to the project file is a reference to Castle.Core. Castle.Windsor is always skipped with the message
- custom nodes for Castle.Windsor ==> skipping".

At least that's how I interpret the output. Would be nice if the warning contained the project's filename to make it easier to find out what's wrong.

I created a Gist containing the project file and the paket.references of the project:
https://gist.github.com/utopius/0eff880c4e47ac9043f9

I'm currently in the middle of cleaning up NuGet mess, I hope I got everything right. Please let me know if you need further info.

@isaacabraham
Copy link
Contributor

This happens (AFAIK) if you have a custom reference to Castle.Windsor already in the project (or if Paket thinks that you do). You can remove this with a restore --hard I believe.

@utopius
Copy link

utopius commented Nov 19, 2014

@isaacabraham thanks,
paket.exe restore --hard did not help, but
paket.exe install --hard did the trick and installed the Castle.Windsor package. The strange thing was: I had no custom reference to it.

@tpluscode Does this fix your problem, too?

@tpluscode
Copy link
Contributor Author

Hm, I redid the conversion from scratch and now I don't have that problem.

So what exactly are the custom nodes? I assumed they were something in the package and not the project.

@tpluscode
Copy link
Contributor Author

Oh, sorry I just got the same problem in the repro solution for issue #372. It can't have anything to do with preexisting references, because that's a fresh csproj created by Visual Studio.

Please have a look at https://github.com/tpluscode/paket-dependencies/blob/master/PaketLocalSources/PaketLocalSources.csproj

I do .paket/paket.exe add nuget FluentAssertions --interactive and answer Yes for the project

@tpluscode
Copy link
Contributor Author

And yes, install --hard does the trick

@forki
Copy link
Member

forki commented Nov 19, 2014

could you please retry with 0.15.1. thanks

@tpluscode
Copy link
Contributor Author

Still doesn't work

@forki
Copy link
Member

forki commented Nov 19, 2014

after removing the wrong path I can reproduce now. Let's see

@forki
Copy link
Member

forki commented Nov 19, 2014

ok I found it.
The issue is the following:
FluentAssertions\lib\sl5 contains Microsoft.CSharp.dll
You project contains a framework reference to Microsoft.CSharp.dll

Now paket is confused and ignores it since we play it conservative.

install --hard gives paket the chance to take over everything.

So I have to classify as "won't fix" and the workaround for this (arguably broken package) is use --hard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants