NuGet is designed to allow you to easily add code libraries to your project. Things like JSON.NET, Entity Framework, etc. Chocolatey is actually built on top of the NuGet package system, but it is designed to fill a different need. Chocolatey wraps up applications and other executables and makes it easy to install them on … Read more
How can I determine where to fix this reference without adding a binding to the app.config? You can try to change the “MSBuild project build output verbosity” to “Detailed” or above to check the detail error log. To do this by Tools -> Options…->Projects and Solutions->Build and Run. Set the MSBuild project build output verbosity level to Detailed or above. … Read more
Taken from this answer. Close your packages.config file. Build Warning is gone! This is the first time I see ignoring a problem actually makes it go away… Edit in 2020: if you are viewing this warning, consider upgrading to PackageReference if you can
In my case, I had to remove the following from the .csproj file: In fact, in this snippet you can see where the error message is coming from. I was converting from MSBuild-Integrated Package Restore to Automatic Package Restore (http://docs.nuget.org/docs/workflows/migrating-to-automatic-package-restore)
You need to add proxy settings into Nuget.Config file. Refer to this link for details: Nuget Config Section & Nuget Proxy Settings.
Menu Tools → Options → Package Manager Give a name and folder location. Click OK. Drop your NuGet package files in that folder. Go to your Project in Solution Explorer, right click and select “Manage NuGet Packages”. Select your new package source. Here is the documentation.
Here’s how I managed to solve it: Go to the solution explorer and choose Antlr under References, right-click and say properties. Make sure the file version is the same the compiler is looking for. In my case, MSBuild wanted version 5.5.0.2, but the reference properties showed an earlier 2.x version. All I had to do is go … Read more