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

Upgrade NuGet.Core to a version that better handles conflict resolution #508

Open
ferventcoder opened this issue Dec 16, 2015 · 10 comments
Open

Comments

@ferventcoder
Copy link
Member

@ferventcoder ferventcoder commented Dec 16, 2015

@ferventcoder ferventcoder self-assigned this Dec 16, 2015
@ferventcoder ferventcoder added this to the 0.9.10 milestone Dec 16, 2015
@ferventcoder

This comment has been minimized.

Copy link
Member Author

@ferventcoder ferventcoder commented Dec 23, 2015

@ferventcoder

This comment has been minimized.

Copy link
Member Author

@ferventcoder ferventcoder commented Jan 5, 2016

This will require .NET 4.5 for the upgrade to a v3 version of NuGet so this will need to move to 0.9.11 0.11.0 where we are eclipsing support for .NET 4 (and Windows 2003).

@ferventcoder ferventcoder modified the milestones: 0.9.11, 0.9.10 Jan 5, 2016
@timbrown5

This comment has been minimized.

Copy link

@timbrown5 timbrown5 commented Jun 30, 2016

Hi ferventcoder,
I know it's a bit early (as 0.9.10 has only just been released) but I was wondering if you have an estimate for when this work might be started. It would be good to test if this fixes the issues I was having (even if it's a development build).

@ferventcoder

This comment has been minimized.

Copy link
Member Author

@ferventcoder ferventcoder commented Jun 30, 2016

It is definitely a bit early. No estimate yet on this.

@timbrown5

This comment has been minimized.

Copy link

@timbrown5 timbrown5 commented Apr 18, 2017

Just wondered if there is any update on when this might be fixed?

@ferventcoder

This comment has been minimized.

Copy link
Member Author

@ferventcoder ferventcoder commented Apr 18, 2017

Looking at late 2017 depending on where it falls in prioritization. Right now it is a few back on the list. We have a pretty aggressive schedule so it could be done in 2017 but it may fall back to 2018.

@timbrown5

This comment has been minimized.

Copy link

@timbrown5 timbrown5 commented Apr 19, 2018

Hi @ferventcoder,
Is there any update on this?
Thanks,
Tim

@ferventcoder

This comment has been minimized.

Copy link
Member Author

@ferventcoder ferventcoder commented Apr 19, 2018

@timbrown5 Note the Milestone - that gives you the best idea on where things are. It's definitely scheduled, but priorities shift based on customer needs, etc.

@eriviere

This comment has been minimized.

Copy link

@eriviere eriviere commented May 22, 2018

What is the current version of NuGet used by Chocolatey?
I am unable to install a NuGet Package because it believes I am using version 2.11 of Nuget. I am actually using choco version 0.10.11

The error is this one:

The 'Microsoft.NETCore.Platforms 2.0.2' package requires NuGet client version '2.12' or above, but the current NuGet version is '2.11.0.0'.

@ferventcoder

This comment has been minimized.

Copy link
Member Author

@ferventcoder ferventcoder commented Jan 18, 2019

@eriviere Chocolatey in what version? It is 2.11, but we're moving it up to 2.14 soon. Hopefully that will make the move up to v3 better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.