nuget / home

Repo for NuGet Client issues

---

NuGet Home

The Home repository is the starting point for people to learn about NuGet, the project. If you're new to NuGet, and want to add packages to your own projects, check our docs. This repo contains pointers to the various GitHub repositories used by NuGet and allows folks to learn more about what's coming in NuGet.

NuGet is being actively developed by the .NET Foundation. NuGet is the package manager for the Microsoft development platform including .NET. The NuGet client tools provide the ability to produce and consume packages. The NuGet Gallery is the central package repository used by all package authors and consumers and has a live deployment at www.nuget.org.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

NuGet Design Proposals

This repo contains design proposals for NuGet. It focuses on designs for the NuGet client tooling, NuGet.org public repository, and NuGet Package Manager inside Visual Studio.

Documentation and Further Learning

NuGet Docs

The NuGet Docs are the ideal place to start if you are new to NuGet. They are categorized in 3 broader topics:

• Consume NuGet packages in your projects;
• Create NuGet packages to learn about packaging and publishing your own NuGet Packages;
• Contribute to NuGet gives an overview of how you can contribute to the various NuGet projects.

NuGet Blog

The NuGet Blog is where we announce new features, write engineering blog posts, demonstrate proof-of-concepts and features under development.

Contributing

There are many ways in which you can participate in the project, for example:

• Submit bugs and feature requests, and help us verify as they are checked in
• Review NuGet proposals
• Review the documentation and make pull requests for anything from typos to new content

If you are interested in fixing issues and contributing directly to the code base, please see the document Contribute To NuGet, which covers the following:

• How to build and run from source
• The development workflow, including debugging and running tests
• Coding guidelines
• Submitting pull requests
• Finding an issue to work on
• And much more!

Note: Not all of our repositories are open for contribution yet. Ping us if unsure.

Feedback

• Ask a question on Stack Overflow
• Request a new feature
• Upvote popular feature requests
• File an issue
• Follow @nuget and let us know what you think!

If you're having trouble with the NuGet.org Website, file a bug on the NuGet Gallery Issue Tracker.

If you're having trouble with the NuGet client tools (the Visual Studio extension, NuGet.exe command line tool, etc.), file a bug on NuGet Home.

Repos and Projects

• NuGet client tools - this repo contains the following clients:
  • NuGet command-line tool 4.0 and higher
  • Visual Studio Extension (2017 and later)
  • PowerShell CmdLets

NuGet.org is backed by several core services:

• NuGetGallery - the current NuGet Gallery
• NuGet.Jobs - NuGet's back-end jobs and services
• ServerCommon - shared libraries for running NuGet.org

NuGet.Server is a lightweight standalone NuGet server.

NuGet Documentation contains NuGet's documentation.

A full list of all the repos is available as well.

NuGet Packages by the NuGet team

We dogfood all of our stuff. NuGet uses NuGet to build NuGet, so to speak. All of our NuGet packages, which you can use in your own projects as well, are available from our NuGet.org profile page.

home's Issues

NuGet.Configuration: ISetting getValue and setValue seems to be case-sentitive for ElementName

while it should not be.

NuGet.PackageManagement: Support roll backs when execution of .ps1 files fail by throwing exceptions from PS layer

Powershell should custom exception PackageAlreadyInstalled from Update-Package to show the right message. Instead of trying to check if there are any updates on its own

so that for the scenario of update-package, it won't throw InvalidOperation of package already exist.
Instead, we should print a message of no package updates available.

NuGet.Protocol: ResolverMetadataClient. IsItemRangeRequired needs to be accurate

NuGet.PackageManagement: Update-All: Test and validate PreviewUpdatePackagesAsync

NuGet.PackageManagement: Not execute init.ps1 of a package, if it is already installed once in a solution

NuGet.PackageManagement: Not execute init.ps1 of a package, if it is already installed once in a solution

NuGet.PackageManagement: Expose dependency graph based on packages folder for init.ps1 to be executed properly on powershell console open

NuGet.PackageManagement: Need to support rollback on install

NuGet.PackageManagement: Need to support rollback on install

NuGet.PackageManagement: Support for Delete on restart when package uninstall is incomplete

NuGet.Powershell: 'Get-Project -All' does not work with projects under solution folders

NuGet.PackageManagement: Uninstalling satellite packages

NuGet.PackageManagement: Uninstalling satellite packages

NuGet.VisualStudioExtension: Binding-Redirects with dependent projects does not work as desired

Binding-Redirects with dependent projects does not work as desired
And, BindingRedirects should only be executed once per user action

NuGet.Packaging: Satellite packages are not supported

NuGet.VisualStudioExtension: Test all functional tests against JS, Win81 and Silverlight in that order

NuGet.PackageManagement: Support IEnumerable of primary repositories because nuget.exe -source switch could be a collection unlike powershell

PackageManagement.VisualStudio: VSSolutionManager.GetNuGetProjectSafeName() is not returning correct names for projects under solution folder

Need to update the logic. So it returns folder\projectName for these insider a folder.

PackageResolver: Resolver failed to resolve the correct identities for Update-Package Id scenario

on NuGetPackageManager's PreviewInstallPackageAsyncPrivate method, the call of
IEnumerable newListOfInstalledPackages = packageResolver.Resolve(packageTargetsForResolver, availablePackageDependencyInfoWithSourceSet, projectInstalledPackageReferences, token);

returns wrong results.
It should have returned jquery.2.1.3 as one of package identities, now it returns jquery.1.4.4.

jQuery 2.1.3 was removed from the following lines of code, which should not be.

                if(installedPackageWithSameId != null)
                {
                    packageTargetsForResolver.Remove(installedPackageWithSameId);
                }

Repro steps:

1. Install-package jquery.validation
2. Update-package jquery

Expected: updates jquery to 2.1.3
Actual: preview install action (install by Id) returns 0 actions.

NuGet.VisualStudioExtension: Add support to cancel automatic package restore

NuGet.Packaging: Issue reading nuspec files with certain namespaces

NuGet.Packaging: Issue reading nuspec files with certain namespaces

UI: Review Changes should use a different order for the display

The order of operations shown in the preview should be:

1. Uninstalling
2. Updating
3. Installing

I thought we displayed packages that were being updated, but I don't see an Updating header anymore. If that's gone, then the order should be:

1. Uninstalling
2. Installing

NuGet.PackageManagement: Resolver gather should throw when all the necessary packages are not gathered

NuGet.PackageManagement: Should not default null for sourceRepositories to mean all the enabled repositories in SourceRepositoryProvider. Preferable to have function overloads or default values

NuGet.PackageManagement: Readme.txt should be executed and for the directly installed package alone

NuGet.PackageManagement: Readme.txt and BindingRedirects should only be executed once per user action

NuGet.CommandLine: Need functional tests for nuget.exe

UI: Action changes to updating previous version after installing

After installing the latest version of a package, the following happens:

1. The Action changes to "Update"
2. The Version changes to the previous version
3. The button changes to "Update"

When selecting a package that is already installed, here's what I'm thinking we should do:

1. If there is an update available, select the latest version (respecting prerelease checkbox) and set the action to Update.
2. If the latest version is already installed, set the action to Uninstall.

NuGet.Frameworks: Framework reducer returns nothing when net40 and net40-client are present in the package

NuGet.Frameworks: Framework reducer returns nothing when net40 and net40-client are present in the package

NuGet.CommandLine: nuget.exe pack is not implemented

NuGet.Powershell: Relative path on '-Source' switch does not work

NuGet.PackageManagement: Minclient Version. Need to throw as appropriate

NuGet.Packaging: Packages with nested folder under lib do not work as desired

NuGet.ProjectManagement: Project specific packages.config should be preserved

NuGet.PackageManagement: Test that DependencyVersion via settings file work as desired

NuGet.Configuration: There should be async versions of ISettings methods such as SetValue, DeleteValue as well

NuGet.Configuration: Methods on ISettings such as SetValue, DeleteValue should be async

NuGet.PackageManagement: PowerShellConsole and UI should expand node and collapse nodes during package actions

in solution explorer.

Right now it's not.

NuGet.Powershell: Piping of project(s) is not supported

NuGet.CommandLine: nuget.exe install <packages.config> is not supported yet

NuGet.PackageManagement: Overwrite actions is not being prompted/effective

Install-package testpackage.overwritetest or use UI to install this package with prompt user selected.

Expected: prompt user to choose overwrite or ignore the file in the package

Actual: nothing happens

NuGet.PackageManagement: Resolver Gather throws null reference for primary package source is a folder

If the dependent package such as Microsoft.aspnet.mvc lives in a folder and use that folder as the primary package source, resolver gather will throw null reference exception at line 40:

        var packageWithNoDependencyInfoInPrimary = (primaryPackages.Where(p => !primaryRepoPackageDependencyInfo
            .Any(pdi => new PackageIdentity(pdi.Id, pdi.Version).Equals(p)))).FirstOrDefault();

here primaryRepoPackageDependencyInfo is null for a local folder repo, because primarySource.GetResource() returns null.

We should do a null check and also process this scenario accordingly.

Repro step:
install-package https://az320820.vo.msecnd.net/packages/microsoft.aspnet.mvc.4.0.20505.nupkg

type above on PMC.

NuGet.PackageManagement: Source Control : When packages folder is not checked-in

NuGet.PackageManagement: Rollback on mid-install failure such as IO or COMExceptions

NuGet.PackageManagement: Uninstalling a package with uninstall.ps1 from powershell console fails

NuGet.PackageManagement: Uninstalling a package with uninstall.ps1 from powershell console fails

Just install and uninstall jQuery from powershell console. Uninstall will work fine but uninstall.ps1 will fail to execute. This is because, in powershell console, today, powershell scripts get executed as post-step at the end in order to avoid thread switching. This does not work for executing uninstall.ps1 since the package directory is already deleted

We have to be able to invoke methods on the powershell dispatcher

NuGet.Protocol: GetLatestVersions on folder repository does not return stable version when includePrerelease is false

NuGet.PackageManagement: If package restore fails, satellite files for the successfully restored packages are not restored

NuGet.PackageManagement: If restoring a package fails, satellite files for the successfully restored packages are not restored

Repro steps:

1. Create a console Application
2. Install-Package Microsoft.AspNet.Razor.fr
3. Install one or more packages from a private feed such that it is not available from NuGet official
4. Now, disable the private feed and only retain the official feed
5. Delete packages folder
6. Initiate restore packages through build or using 'Restore' button on the UI window
7. Package restore will fail for all the packages from the private feed

Expected:

Satellite files for the Microsoft.AspNet.Razor.Fr is copied successfully

Actual:

Satellite files are not copied for Microsoft.AspNet.Razor.Fr and it never becomes available for restore again

NuGet.Packaging: Package extractor does not non-file entries from ZipArchive and fails

UI: Installed filter doesn't show glyph for updates available

Repro:

1. Install log4net 2.0.2 (the latest version is 2.0.3)
2. Select the Installed filter

Expected:

1. log4net would show with the update available glyph

Actual:

1. log4net shows up with the installed/latest checkmark glyph

NuGet.Packaging: Satellite package which does not have exact version of runtime package in dependency version spec do not work

NuGet.Packaging: Satellite package which does not have exact version of runtime package in dependency version spec do not work

NuGet.Packaging: Need to re-enable framework specific content files

NuGet.PackageManagement: Use DownloadResource.Progress event

NuGet.PackageManagement: Use DownloadResource.Progress event

Repro steps

1. Create a console application
2. From the powershell console, install a fairly large package, say, EntityFramework

Expected:

1. There is a progress bar at the bottom-right of powershell console

Actual:

1. There is no progress bar at the bottom-right of powershell console. When downloading a large package, there is no visual feedback to the user

NuGet.Protocol: VS Crashes: It should not assert when failing to create the V2 repository

Sometimes people type in incorrect input for -source switch, which will cause creation of V2 repository to fail.

It now will crash VS after debug.assert.

NuGet.PackageManagement: powershell cmdlets does not work on project K

reported by Fei