Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

Add "restore_tools" that gets a new NuGet version for a workaround #224

Closed
wants to merge 1 commit into from

Conversation

dagood
Copy link
Member

@dagood dagood commented Jul 22, 2016

To work around NuGet/Home#3190 the recommended way, core-setup needs a new version of NuGet to use --disable-parallel to limit HTTP parallelism during build_projects restore.

There is a chance that restoring restore_projects will time out just like build_projects does, but there are fewer dependencies so it's less likely.

@dnfclas
Copy link

dnfclas commented Jul 22, 2016

Hi @dagood, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!

The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.

TTYL, DNFBOT;

@dagood
Copy link
Member Author

dagood commented Jul 25, 2016

Errors here are due to case sensitivity incompat between restore in the NuGet version I pull in and build in CLI stage_0. Since the case insensitivity change was merged before the change that adds the workaround into NuGet, there's no compatible NuGet version. Barring another layer of workarounds, this isn't going to work with what's out there.

There is a CLI PR out to support the new casing: dotnet/cli#2722. That would make this PR work, but since that PR also upgrades NuGet, it makes this workaround project redundant. Closing.

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

Successfully merging this pull request may close these issues.

2 participants