forked from NuGet/NuGet.Client
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
(NuGet#9) Renamed NuGet.Frameworks project
To be Chocolatey.NuGet.Frameworks. Due to a transitive dependency from one of the Microsoft Unit Testing libraries on the NuGet.Frameworks NuGet package, it wasn't possible to directly renamed the NuGet.Frameworks project to Chocolatey.NuGet.Frameworks in the same way that we have done the other projects. When we tried this, there was a conflict between the assemblies, and it wasn't possible to compile. We attempted to use the standard solutions like introduce an app.config file to redirect the binding, but none of these approches worked. Various solutions were put forward, including using an assembly alias and extern inclusion, as well as completely removing the NuGet.Frameworks project reference in favour of the upstream NuGet.Frameworks NuGet package, but all of these were rulred out in favour of renaming the project and the assemblies, and then updating the using statements and various other places where the name is used. It is understood that there will likely be similar changes required when we pull in upstream code from the NuGet.Client GitHub repository.
- Loading branch information
Showing
484 changed files
with
6,977 additions
and
2,046 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.