-
Notifications
You must be signed in to change notification settings - Fork 526
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
Incompatible dependency with Microsoft.AspNetCore.All 2.0.0-preview2-final #2557
Comments
"It should work as Nuget". Can you elaborate on this please? What version do you expect to be pulled down? Why? |
Well, we are migrating the project to .Net Core and the first step was to make it work with Nuget. And it works i.e. we do not have any dependency problem. Now, we want to integrate Paket: so I create my paket.dependencies and I don't even specify the Microsoft.CSharp dependency as I don't care i.e it is a third party dependency. Well, logically the version to use is the last one (the 4.4 preview) which is supposed to be compatible as everything works with Nuget. |
this is a really hard problem. But I'm working on a fix that allows users to relax the conditions |
Well, personnally I don't see where is the conflict: as soon as the version 4.4 will be released, this problem will disapear if I'm not wrong. So there is no conflict. The problem is only because the resolution has to specify that it accepts prerealese versions explicitly which nobody never does in nuspec because Nuget cannot have the same problem. But I may be wrong. |
the problem is that some package in the chain explicitily require releases. |
Ok. As soon as you have a solution, I will not disagree :) |
@xlegalles for now you can just add all packages you want to allow as prerelease to your Solving this problem is quite a lot harder than it seems. We'd really like to do it, as it hurts for this particular situation (which happens quite often when using single prereleases). On the other hand providing a consistent resolution is more important than "locking" an incorrect one (which basically has happened in paket 4). That's one of the design goals of paket after all. |
Thank you for the tip as it seems to work: I'm now deeper in the dependency graph and adding prerelease condition one by one... |
@xlegalles yeah that is a workaround. 39a60cf is a potential fix. It resolves
to
|
@xlegalles I released a prerelease with a fix. could you please give it a try? |
Description
I got
Incompatible dependency: Microsoft.CSharp >= 4.4.0-preview2-25405-01 conflicts with resolved version 4.3.0
while trying to useMicrosoft.AspNetCore.All 2.0.0-preview2-final
with Paket version 5.81.1.The problem is impossible to solve because
Microsoft.AspNetCore.All 2.0.0-preview2-final
requires:Microsoft.AspNetCore.JsonPatch 2.0.0-preview2-final
which itself requiresMicrosoft.CSharp >= 4.4.0-preview2-25405-01
Microsoft.AspNetCore.Localization 2.0.0-preview2-final
which itself requiresMicrosoft.CSharp >= 4.3
So both third-party dependencies specify different constraints with Microsoft.CSharp which are incompatible from paket point of view.
Expected behavior
It should work as Nuget.
Known workarounds
None.
The text was updated successfully, but these errors were encountered: