Yes you can! http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages The current NuGet workflow has always been to commit the Packages folder into source control. The reasoning is that it matches what developers typically do when they don’t have NuGet: they create a ‘Lib’ or ‘ExternalDependencies’ folder, dump binaries into there and commit them to source control to allow others to … Read more
Close the solution then go to the packages folder on your hard drive and delete all its contents. Open your application again in Visual Studio and it will automatically try to restore the packages. Clean the Solution and Build it.
dotnet pack – Produces a NuGet package of your code. That is the key difference – this will enable to publish to http://nuget.org, or to a nuget server that can be pulled down by other developers, or even for use with Octopus Deploy. dotnet publish – Produces a .NET framework-dependent or self-contained application. Keyword is … Read more
VisualStudio 2019: Tools > Nuget Package Manager > Package Sources: Select nuget.org and specifically unselect the others options
Solution Explorer->Right Click on Project Name -> Click on Manage Nuget Packages -> Search for newtonsoft -> Click on install button
I ran into this issue as well. In my case, when the DLL was packaged and placed in the lib/ folder, the import warning occurred. It was solved by placing the packaged DLL in the lib/netstandard2.0 folder.
I had to change using Microsoft.Practices.unity; to using Unity; I think because of an update in Unity with NuGet
As of 2020 there is no officially supported way to do this. However various people have come up with ways to achieve it, and the current best way is to install a NuGet package prepared by the amazing Teroneko. Then all you need to do is edit your .csproj to update all your project to … Read more
A custom tool called dotnet depends is great for viewing reverse dependencies. Installation: dotnet tool install –global dotnet-depends Usage: dotnet depends .\MyProject.csproj NuGet 6.3 in Visual Studio also shows this if you hover over the transitive package.
UPD 2024: standalone nuget commands replaced with dotnet nuget CLI. The information provided is relevant for VS2022 and .NET 8. Cache locations Solution-local packages folders are no longer used by .NET Core and Visual Studio. The command to list user-specific folders is: dotnet nuget locals all –list And its typical output (I’ve replaced absolute paths … Read more