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

Lowercase ID and version in NuGet global packages directory #2722

Closed
wants to merge 23 commits into from

Conversation

joelverhagen
Copy link
Member

@joelverhagen joelverhagen commented Apr 27, 2016

This pulls in the latest version of NuGet, which writes packages to the global packages directory with a lowercase ID and version.

Bump NuGet version to 3.5.0-rc-1298.


This change is Reviewable

@joelverhagen
Copy link
Member Author

joelverhagen commented May 4, 2016

/cc @piotrpMSFT @pakrym (please CC other people I am missing)

Does these changes look reasonable? I would like to iron out objections to these changes before committing my changes to NuGet (as they are breaking). Once I get sign off, I will create new PR pointing to the real NuGet bits.

@joelverhagen joelverhagen force-pushed the jver/pathprop branch 3 times, most recently from ab22b14 to c3cc65e Compare May 11, 2016 15:42
@joelverhagen joelverhagen force-pushed the jver/pathprop branch 3 times, most recently from ac724c9 to f4e5b90 Compare May 13, 2016 00:03
@joelverhagen joelverhagen changed the title [WIP] Lowercase ID and version in NuGet global packages directory Lowercase ID and version in NuGet global packages directory May 13, 2016
@joelverhagen joelverhagen changed the title Lowercase ID and version in NuGet global packages directory [WIP] Lowercase ID and version in NuGet global packages directory May 13, 2016
@@ -73,7 +76,10 @@ public void ResolvesAllAssemblies()
[Fact]
public void FailsWhenOneOfAssembliesNotFound()
{
var packagePath = Path.Combine(PackagesPath, F.DefaultPackageName, F.DefaultVersion);

This comment was marked as spam.

This comment was marked as spam.

@joelverhagen
Copy link
Member Author

Until I come up with a solid plan to synchronize a core-setup PR (dotnet/core-setup#64) and this PR, this change is on hold.

eerhardt added a commit to eerhardt/cli that referenced this pull request Jul 26, 2016
The new NuGet uses tolower paths, and we need to react to it.

Port dotnet#2722
Port dotnet#3554
eerhardt added a commit to eerhardt/cli that referenced this pull request Jul 27, 2016
The new NuGet uses tolower paths, and we need to react to it.

Port dotnet#2722
Port dotnet#3554
livarcocc pushed a commit to livarcocc/core-setup that referenced this pull request Aug 3, 2016
The new NuGet uses tolower paths, and we need to react to it.

Port dotnet/cli#2722
Port dotnet/cli#3554
livarcocc pushed a commit to livarcocc/core-setup that referenced this pull request Aug 3, 2016
The new NuGet uses tolower paths, and we need to react to it.

Port dotnet/cli#2722
Port dotnet/cli#3554
@joelverhagen
Copy link
Member Author

Talked to @eerhardt about this PR. In addition to #3554, he has ported this work into the feature/msbuild branch. Therefore, I can close this PR.

@joelverhagen joelverhagen deleted the jver/pathprop branch August 31, 2016 23:45
pranavkm pushed a commit that referenced this pull request Dec 7, 2016
The new NuGet uses tolower paths, and we need to react to it.

Port #2722
Port #3554
pranavkm pushed a commit that referenced this pull request Dec 7, 2016
The new NuGet uses tolower paths, and we need to react to it.

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

Successfully merging this pull request may close these issues.

10 participants