-
Notifications
You must be signed in to change notification settings - Fork 525
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
Comments
can you please show us the csproj file? |
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 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: 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. |
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. |
@isaacabraham thanks, @tpluscode Does this fix your problem, too? |
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. |
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 |
And yes, |
could you please retry with 0.15.1. thanks |
Still doesn't work |
after removing the wrong path I can reproduce now. Let's see |
ok I found it. 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 |
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
orupdate
it says in yellowcustom 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.The text was updated successfully, but these errors were encountered: