You need use the NuGet command line in the Package Manager Console: Update-Package -reinstall to force reinstall the package references into project. NuGet Restore only restores files in the packages directory (\packages folder ), but does not restore files inside your project or otherwise modify your project. For example, if a package has added some … Read more
I have a similar situation with external and internal package sources with projects referenced in more than one solution. I just got this working with one of our code bases today and it seems to be working with the developer workstations and our build server. The below process has this scenario in mind (although it … Read more
Here’s what I did to get this working with my corporate proxy that uses NTLM authentication. I downloaded NuGet.exe and then ran the following commands (which I found in the comments to this discussion on CodePlex): nuget.exe config -set http_proxy=http://my.proxy.address:port nuget.exe config -set http_proxy.user=mydomain\myUserName nuget.exe config -set http_proxy.password=mySuperSecretPassword This put the following in my NuGet.config … Read more
It took far too long but I finally found this document on Migrating MSBuild-Integrated solutions to Automatic Package Restore and I was able to resolve the issue using the methods described here. Remove the ‘.nuget’ solution directory along from the solution Remove all references to nuget.targets from your .csproj or .vbproj files. Though not officially … Read more
I want to create a nuget package which adds multiple .dll as references to my project. I would like give you two solutions to achieve this: First, Use NuGet Package Explorer： Download the NuGet Package Explorer. Open the NuGet Package Explorer, select the create a new package. Add a lib folder on the content tab, … Read more
Using the Copy target in the targets file to copy required libraries won’t copy those files to other projects which reference the project, resulting in a DllNotFoundException. This can be done with a much simpler targets file though, using a None element, as MSBuild will copy all None files to referencing projects. <Project xmlns=”http://schemas.microsoft.com/developer/msbuild/2003″> <ItemGroup> … Read more
You can use nuget.exe to restore your packages or with NuGet 2.7, or above, installed you can simply compile your solution in Visual Studio, which will also restore the missing packages. For NuGet.exe you can run the following command for each project. nuget install packages.config Or with NuGet 2.7 you can restore all packages in … Read more
Instead of using a PowerShell script another approach is to use an MSBuild targets or props file with the same name as the package id: <Project xmlns=”http://schemas.microsoft.com/developer/msbuild/2003″> <ItemGroup> <None Include=”$(MSBuildThisFileDirectory)importantfile.xml”> <Link>importantfile.xml</Link> <CopyToOutputDirectory>Always</CopyToOutputDirectory> </None> </ItemGroup> </Project> In the nuspec file then, instead of adding the required files to the Content directory, add them to the Build … Read more
First, download the NuGet command line tool from here. Next, open a command prompt and cd to the directory to which nuget.exe was downloaded. You can list the local caches with this command: nuget locals all -list You can clear all caches with this command: nuget locals all -clear Reference: https://docs.nuget.org/consume/command-line-reference
You can add this to a <PropertyGroup> inside your csproj file to enforce copying NuGet assemblies to the build output: <CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies> However, note that the build output (bin/Release/netcoreapp*/*) is not supposed to be portable and distributable, the output of dotnet publish is. But in your case, copying the assemblies to the build output is probably … Read more