I&#39;m going to bang out a couple of questions here...first, with NuGet is it possible to create a package from a few DLLs? There is no visual studio project, just the command line and a couple of pre-compiled DLL files. 

Second, assuming that is possible, why do I continuously get the &quot;Assembly outside of the lib folder&quot; warning? I&#39;ve tried everything I can think of to get associated assemblies to add themselves as references inside of the NuGet package. 

My file structure looks like this

     Root
       - File1.dll
       - lib
         - File2.dll
         - File3.dll

When I tell NuGet to pack it using a .nuspec like this

    &lt;?xml version=&quot;1.0&quot;?&gt;
    &lt;package &gt;
      &lt;metadata&gt;
        &lt;id&gt;File1.dll&lt;/id&gt;
        &lt;version&gt;1.0.0&lt;/version&gt;
        &lt;authors&gt;thisguy&lt;/authors&gt;
        &lt;owners&gt;thisguysmom&lt;/owners&gt;
        &lt;requireLicenseAcceptance&gt;false&lt;/requireLicenseAcceptance&gt;
        &lt;description&gt;This is some library&lt;/description&gt;
        &lt;releaseNotes&gt;Porting to NuGet&lt;/releaseNotes&gt;
        &lt;copyright&gt;Copyright 2012&lt;/copyright&gt;
        &lt;references&gt;
    	  &lt;reference file=&quot;File2.dll&quot; /&gt;	  
    	  &lt;reference file=&quot;File3.dll&quot; /&gt;
    	&lt;/references&gt;
      &lt;/metadata&gt;
    &lt;/package&gt;

I receive that warning. From what I&#39;m reading, I shouldn&#39;t even have to define the references node in any of my projects, as the lib folder items should automatically be added as references?

Does anyone out there understand this NuGet mess?

NuGet Assembly outside lib folder

I am attempting to publish and consume versioned NuGet packages of class libraries while avoiding headaches for local development. Here is a sample Visual Studio solution layout:

    | Libraries
      | LibraryA
      | LibraryB
      | LibraryC
    | Applications
      | ApplicationD
      | ApplicationE

This is a single solution containing both shared class libraries and multiple applications. Currently references to the class libraries by the applications are local in-solution references.

What I would like to do is to publish the libraries (A,B,C) as versioned NuGet packages which are then referenced by the applications as needed (D,E). This allows a change to a shared library to be independent from an update to an application which is deployed. Without this, changing one library could cause the binaries to change in a dozen or more applications, all of which would technically need to be tested. This is undesirable, and versioning with NuGet fixes this.

However, let us say that I want to update the content of LibraryA and ApplicationD at the same time. In order to do this after we have switched to NuGet, I will have to make changes to LibraryA, commit them, wait for the package to be created, tell ApplicationD to update its reference to LibraryA, and then test or develop in ApplicationD. This is far more complicated than simply working with both at the same time using local in-solution references.

What is a better way to get both the robustness of versioned NuGet packages for my shared class libraries while also keeping development simple even if it spans over multiple projects and applications? The only other solutions I have found all involve too much overhead or headache, such as having to constantly change the references for ApplicationD between the NuGet package and the local project.

**EDIT:** To clarify the premise, this question assumes the following:

 - The architecture (solution and project organization) cannot be significantly reorganized
 - Shared libraries are going to change at a non-trivial frequency
 - Changing a shared library cannot force any application to be updated
 - Applications can reference different versions of shared libraries

Pain-free local development while also referencing NuGet packages

I have the following convention for most of my projects:

    /src
        /Solution.sln
        /SolutionFolder
            /Project1
            /Project2
            /etc..
    /lib
        /Moq
            moq.dll
            license.txt
        /Yui-Compressor
            yui.compressor.dll
    /tools
        /ILMerge
            ilmerge.exe

You&#39;ll notice that I do *not* keep external libraries *inside* the source folder. I&#39;m also very interested in using NuGet but don&#39;t want these external libraries inside the source folder. Does NuGet have a setting to change the directory that all packages are loaded into?

Is it possible to change the location of packages for NuGet?

I&#39;m trying to upgrade a .net core 2.1 project to the latest version of Nuget packages such as Microsoft.Extensions.DependencyInjection.Abstractions 2.1.1.

However this is blocked by the package reference Microsoft.NETCore.App, when I try to upgrade the &quot;meta&quot; package Microsoft.NETCore.App I see &quot;Blocked by project&quot; similar to [this question](https://stackoverflow.com/questions/44026190/visual-studio-2017-cannot-update-microsoft-netcore-app-package-blocked-by-proj). That was resolved by switching to the newer version of the SDK, however that isn&#39;t an option here... because there isn&#39;t a newer version of the SDK (yet?).

I&#39;ve also seen [this answer](https://stackoverflow.com/a/43917843/31151) to upgrade specific packages by editing the .csproj file manually with an Update package reference but I doubt that&#39;s the intended method of doing this.

How *should* I go about this? For now I&#39;ve just manually included the package references I actually use and dropped the meta package but I can&#39;t imagine that&#39;s the intended way to go about this.


Microsoft.AspNetCore.App 2.1.1 upgrade &quot;Blocked by project&quot;

An MVC app broke after we updated all the NuGet packages. After trying everything I created a new MVC app, updated the NuGet packages and the basic navbar...

    &lt;div class=&quot;navbar navbar-inverse navbar-fixed-top&quot;&gt;
        &lt;div class=&quot;container&quot;&gt;
            &lt;div class=&quot;navbar-header&quot;&gt;
                &lt;button type=&quot;button&quot; class=&quot;navbar-toggle&quot; data-toggle=&quot;collapse&quot; data-target=&quot;.navbar-collapse&quot;&gt;
                    &lt;span class=&quot;icon-bar&quot;&gt;&lt;/span&gt;
                    &lt;span class=&quot;icon-bar&quot;&gt;&lt;/span&gt;
                    &lt;span class=&quot;icon-bar&quot;&gt;&lt;/span&gt;
                &lt;/button&gt;
                &lt;a class=&quot;navbar-brand&quot; href=&quot;/&quot;&gt;Application name&lt;/a&gt;
            &lt;/div&gt;
            &lt;div class=&quot;navbar-collapse collapse&quot;&gt;
                &lt;ul class=&quot;nav navbar-nav&quot;&gt;
                    &lt;li&gt;&lt;a href=&quot;/&quot;&gt;Home&lt;/a&gt;&lt;/li&gt;
                    &lt;li&gt;&lt;a href=&quot;/Home/About&quot;&gt;About&lt;/a&gt;&lt;/li&gt;
                    &lt;li&gt;&lt;a href=&quot;/Home/Contact&quot;&gt;Contact&lt;/a&gt;&lt;/li&gt;
                &lt;/ul&gt;
                
    &lt;ul class=&quot;nav navbar-nav navbar-right&quot;&gt;
        &lt;li&gt;&lt;a href=&quot;/Account/Register&quot; id=&quot;registerLink&quot;&gt;Register&lt;/a&gt;&lt;/li&gt;
        &lt;li&gt;&lt;a href=&quot;/Account/Login&quot; id=&quot;loginLink&quot;&gt;Log in&lt;/a&gt;&lt;/li&gt;
    &lt;/ul&gt;


            &lt;/div&gt;
        &lt;/div&gt;
    &lt;/div&gt;


... looks like this ...

[![NavBar][1]][1]

...and clicking the icon...

[![NavBar Open][2]][2]

Any ideas what could be causing this?

Have tried manually adding Bootstrap.css and Bootstrap.js to _Layout.vbhtml, but no difference

Thank you


  [1]: https://i.stack.imgur.com/VkNu1.png
  [2]: https://i.stack.imgur.com/flggT.png

MVC bootstrap navbar not working after running NuGet updates

I have two repositories, and I need compiled libraries from one repository in the other. I don&#39;t want to manually check repo1 for updated libraries, and copy/commit to repo2, because that is stupid. I&#39;ve got repo1 building NuGet packages on each build of the necessary libraries, and publishing them to an internal NuGet server. Projects in repo2 can then reference these NuGet packages, and everything is (almost) working. 

The one last hurdle to this is automatically updating the NuGet packages in repo2&#39;s projects. Since I don&#39;t know when the libraries in repo1 will get updated (and I shouldn&#39;t have to), I would like some sort of build event on the projects in repo2 that will automatically update the NuGet packages. I currently just have a pre-build event doing it, but since packages.config files contain the version number of the installed package, I keep getting modified files in repo2 (the packages.config files get updated).

So my question is: what&#39;s a good way to automatically upgrade NuGet packages without mucking up my repo2 VCS? ScottGu says [Here][1] (in comments) that it&#39;s possible to hook package upgrades up to CI builds, but he doesn&#39;t specify how and my current solution is messy. Is there a built in way that I&#39;m missing? Or any better work-arounds? 


  [1]: http://weblogs.asp.net/scottgu/archive/2010/10/06/announcing-nupack-asp-net-mvc-3-beta-and-webmatrix-beta-2.aspx#7624506

How to automatically update NuGet packages to latest available version

How can I install a Nuget Package in Visual Studio Code? I know in Visual Studio, we  can do this through the Nuget Package Manager console, but how do I do it in VS Code?

Install a Nuget package in Visual Studio Code

All of a sudden, I am getting this error when upgrading Nuget packages.  None of the fixes that I have come across work.  I am using Visual Studio 2013.

&gt; &#39;Newtonsoft.Json 6.0.3&#39; already installed.
&gt; 
&gt; Adding &#39;Newtonsoft.Json 6.0.3&#39; to Tournaments.Notifications.
&gt; 
&gt; Successfully added &#39;Newtonsoft.Json 6.0.3&#39; to Tournaments.Notifications.
&gt; 
&gt; Executing script file &#39;F:\My Webs\BasketballTournaments\MainBranch\packages\Newtonsoft.Json.6.0.3\tools\install.ps1&#39;.
&gt; 
&gt; Failed to initialize the PowerShell host. If your PowerShell execution policy setting is set to AllSigned, open the Package Manager Console to initialize the host first.

**Package Manager Console**

&gt; Attempting to perform the InitializeDefaultDrives operation on the &#39;FileSystem&#39; provider failed.

If I wait for the initialization to finish in the console I was able to add some packages.

Can&#39;t install nuget package because of &quot;Failed to initialize the PowerShell host&quot;

I am getting the following error:

    

&gt; [A]System.Web.WebPages.Razor.Configuration.HostSection cannot be cast
&gt; to [B]System.Web.WebPages.Razor.Configuration.HostSection. Type A
&gt; originates from &#39;System.Web.WebPages.Razor, Version=2.0.0.0,
&gt; Culture=neutral, PublicKeyToken=31bf3856ad364e35&#39; in the context
&gt; &#39;Default&#39; at location
&gt; &#39;C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.WebPages.Razor\v4.0_2.0.0.0__31bf3856ad364e35\System.Web.WebPages.Razor.dll&#39;.
&gt; Type B originates from &#39;System.Web.WebPages.Razor, Version=3.0.0.0,
&gt; Culture=neutral, PublicKeyToken=31bf3856ad364e35&#39; in the context
&gt; &#39;Default&#39; at location &#39;C:\Users\MyName\AppData\Local\Temp\Temporary
&gt; ASP.NET
&gt; Files\root\63e7ff36\a1cb775d\assembly\dl3\8f568c18\9b7ddacf_d04dcf01\System.Web.WebPages.Razor.dll&#39;.

I have searched across stackoverflow for similar issues and I used their solutions but it doesn&#39;t seem to fix the issue I am experiencing.

It suddenly occurred, I just pressed clean solution and this error popped up. I also started using nuget package restore on the solution. I updated my packages as well (using Update-package) so one of those might have something to do with this issue. 
 

[A]System.Web.WebPages.Razor.Configuration.HostSection cannot be cast to... web.config issue

I have been using NuGet to retrieve packages from external and internal package sources, which is very convenient. But I have realized that the packages are by default stored per solution, which is very frustrating when some projects with NuGet references are included in several solutions. Then the references are changed to other solutions package folder which may actually be unavailable to another developer or build machine.

I have seen that there are ways to point out a common package location (perhaps at the project root level, we are using TFS source control) with the release 2.1 of NuGet, see [release notes][1] . I am using NuGet v2.7

But I have tried to add nuget.config files without seeing any effect of this. Packages are still stored in the solution folder. Is there anything I have missed?
There seems to be different structures of the xml node to add to the nuget.config file, depending on who is answering that question:
Schwarzie suggests on [another Stackoverflow thread][2]:

    &lt;settings&gt;
      &lt;repositoryPath&gt;..\..\[relative or absolute path]&lt;/repositoryPath&gt;
    &lt;/settings&gt;

The release notes for NuGet 2.1 (see link above) suggests this format: 

    &lt;configuration&gt;
      &lt;config&gt;
        &lt;add key=&quot;repositoryPath&quot; value=&quot;..\..\[relative or absolute path]&quot; /&gt;
      &lt;/config&gt;
    &lt;/configuration&gt;

I don&#39;t know which one of these, or any, or both will work in the end. I have tried both at solution level. 
Can the nuget.config file be placed on TFS project root level, or must it be in the solution directory? It seems that NuGet reads and applies the settings from these files in a certain order, why it would make sense to add them in several levels, where a nuget.config file on solution level would override one on the TFS project root level. Can this be clarified?


Do I need to remove all installed packages before those references will work?
I would love if someone could provide a step-by-step instruction for moving from solution-specific nuget usage to a common package folder where projects that belong to several solutions can find their required nuget packages.

  [1]: http://docs.nuget.org/docs/release-notes/nuget-2.1#Specify_%e2%80%98packages%e2%80%99_Folder_Location
  [2]: https://stackoverflow.com/questions/8620437/how-to-use-nuget-with-more-than-one-solution

Setting up a common nuget packages folder for all solutions when some projects are included in multiple solutions

I&#39;m trying to create NuGet package for a .Net assembly which does pinvoke to a native win32 dll.
I need to pack both the assembly and the native dll with the assembly added to the project references (no problem at this part) and the native dll should be copied into the project output directory or some other relative directory.

My questions are:

 1. How do I pack the native dll without visual studio trying to add it into the references list?
 2. Do I have to write an install.ps1 for copying the native dll? If so how can I access the package content for copying it?

Add native files from NuGet package to project output directory

I am trying to create a nuget package using http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-package#From_a_convention_based_working_directory
as a reference.
My Package Manger Console in Visual Studio is not allowing me to use the &#39;nuget&#39; command.
I am able to &#39;Get-help nuguet&#39; and it displays:

 The following NuGet cmdlets are included.

        Cmdlet					Description
        ------------------		----------------------------------------------
        Get-Package				Gets the set of packages available from the package source.

        Install-Package			Installs a package and its dependencies into the project.

        Uninstall-Package		Uninstalls a package. If other packages depend on this package, 
                                the command will fail unless the –Force option is specified.

        Update-Package			Updates a package and its dependencies to a newer version.

        Add-BindingRedirect		Examines all assemblies within the output path for a project
                                and adds binding redirects to the application (or web) 
                                configuration file where necessary.
                            
        Get-Project				Returns a reference to the DTE (Development Tools Environment) 
                                for the specified project. If none is specifed, returns the 
                                default project selected in the Package Manager Console.

        Open-PackagePage        Open the browser pointing to ProjectUrl, LicenseUrl or 
                                ReportAbuseUrl of the specified package.

        Register-TabExpansion	Registers a tab expansion for the parameters of a command.


 - 
However, whenever I start off commands with nuget is gives :

The term &#39;nuget&#39; is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try ag
ain.

At line:1 char:6
 + nuget &lt;&lt;&lt;&lt; 
    + CategoryInfo          : ObjectNotFound: (nuget:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
 


I have tried the following solutions:

1&gt;closing down all items and restarting

2&gt; uninstalling and reinstalling

3&gt;creating a powershell profile file (this didn&#39;t exist before and this actually broke everything)

The problem started to appear after I upgraded my Visual Studio 2012 Ultimate trial version to registered. I had originally had the VS 12 Pro installed. I don&#39;t know if that really has anything to do with it but I noticed that others that had similar problems have vs 10 and 12 installed.


My question is &quot;does anyone know what else to try?&quot; My theory is that the path to the nuget command is missing but I cannot find how to configure the paths the package manager console uses and I am not sure where the cmdlet nuget is actually stored. 

Updated---tried downloading the command line tool as suggested below. This lead to  nothing working again. I tried to uninstall and now I have a item in vs2010 extentions for nuget that doesn&#39;t have a install or unistall button enabled. This leads me to believe that it has to do with extensions installed via 2010 and 2012 that has a part in my little drama. If anyone also knows how to nuke an uninstallable extension, please advise also but I will try another question for that. 


&#39;nuget&#39; is not recognized but other nuget commands working

There is a framework-level navigation element at Microsoft Docs called [&quot;.NET Platform Extensions&quot;][1]. It contains docs on recently added APIs like `System.IO.Pipelines` and `System.Threading.Channels` for example, as well as a whole bunch of other APIs, including the not-so-recent ones.

Some APIs from this collection are available as nuget packages (for both .Net Core and .Net Framework), but others are not seemingly available. Also, as of now, there is no nuget package called &quot;.NET Platform Extensions&quot; or anything similar.

So, the question is what exactly does this collection of APIs represent? What is it&#39;s relationship to each of the following:

 - .Net Framework
 - .Net Core
 - .Net Standard

What about support in the .Net Framework / .Net Core?

Finally, some APIs seem to be already available as separate nuget packages, others are yet to be made available, so what is the story in that regard?

  [1]: https://docs.microsoft.com/en-us/dotnet/api/index?view=dotnet-plat-ext-2.1

What are .NET Platform Extensions on docs.microsoft.com?

Using [Azure Functions][1], can I reference and use NuGet packages in my C# function?


  [1]: http://functions.azure.com

How can I use NuGet packages in my Azure Functions?

I am creating a NuGet package for a C# class library, and I would like to include generated Xml Documentation with the library. This is my nuspec file:

``` lang-xml
&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
&lt;package&gt;
  &lt;metadata&gt;
    &lt;id&gt;MyLibrary&lt;/id&gt;
    &lt;version&gt;1.0.0.0&lt;/version&gt;
    &lt;authors&gt;John Nelson&lt;/authors&gt;
    &lt;language&gt;en-US&lt;/language&gt;
    &lt;description&gt;A C# class library&lt;/description&gt;
  &lt;/metadata&gt;
  &lt;files&gt;
    &lt;file src=&quot;..\..\build\MyLibrary.dll&quot; target=&quot;lib\Net40&quot; /&gt;
    &lt;file src=&quot;..\..\build\MyLibrary.xml&quot; target=&quot;lib\Net40&quot; /&gt;
  &lt;/files&gt;
&lt;/package&gt;
```

When I [build the package with this command](http://docs.nuget.org/create/creating-and-publishing-a-package):

    nuget pack MyLibrary.nuspec

It generates an error. If I remove the line:

    &lt;file src=&quot;..\..\build\MyLibrary.xml&quot; target=&quot;lib\Net40&quot; /&gt;

NuGet.exe successfully creates the nupkg. I can even unzip the package, and verify that the contents are correct. What am I doing wrong? Should the xml file go into a different target directory?


How do you include Xml Docs for a class library in a NuGet package?

Opening VS2010 today, the extension manager notified me of an update for NuGet Package Manager.

During the install, I get an &#39;Installation Failed&#39; with an option to view the log.

The key error message I see in that log file is:

    The signature on the update version of &#39;NuGet Package Manager&#39; does not match 
    the signature on the installed version. Therefore, Extension Manager cannot 
    install the update.

The version numbers I am upgrading from/to are as follows.

    Current Version: 1.5.20902.9026  
    New Version: 1.6.21205.9031

I have also tried to install it while VS2010 is closed via this page:
[here][1]


  [1]: http://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c

NuGet Package Manager errors when trying to update

I can clear my development computer&#39;s NuGet package cache using Visual&amp;nbsp;Studio menu *Tools* &amp;rarr; *Options* &amp;rarr; *NuGet Package Manager* &amp;rarr; *General*: &lt;kbd&gt;Clear Package Cache&lt;/kbd&gt; button.

I would like to do this on the command line. Unfortunately, I can not find a related command line switch for nuget.exe.

Did I miss something?





How can I clear the NuGet package cache using the command line?

I want to [run a local/internal NuGet repository][1].  I think I&#39;ve figured out how to &quot;reuse&quot; existing NuGet packages by including them in a dummy project using NuGet and scanning the package file to [grab my locally-cached `.nupkg` files][2], but...

## How do you create a nuget package (`.nupkg`) from a project, automatically including **all** `dll` dependencies and not just those grabbed via NuGet?

Specifically:

1. Create a solution
2. Add a new Project
3. Add references to various `.dll` files/other projects _&lt;-- this is the missing part_
4. Add NuGet packages via package manager / cmdline / whatever
5. _something_ automatically creates the `.nupkg`

From what I&#39;ve found, you&#39;re supposed to do things like

* manually edit your `.csproj` file to add `&lt;BuildPackage&gt;true&lt;/BuildPackage&gt;` to include dependencies
* manually create a `.nuspec` file and manually [list your dependencies][3] ([similar ?][4])
* manually run `nuget pack` on your `.nuspec` file

But everything is manual, which is stupid.  Even the semi-automatic solutions are still awkward or half-manual:

* [Create `.nuspec` templates][5] - doesn&#39;t seem to include dependencies, just metadata
* [nuget pack via build-event][6] (step #5), which you need to add manually to every project, and it has [its own quirks][7]:

        &quot;$(SolutionDir).nuget\NuGet.exe&quot; pack &quot;$(ProjectPath)&quot; -Properties Configuration=Release
        move /Y *.nupkg &quot;$(TargetDir)&quot;

I&#39;ll settle for something that automatically creates a `.nuspec` manifest from project references.  Then theoretically that + the nuget build-event can be rolled up into a build-project/nuget package, which is what I really want to see.

  [1]: http://haacked.com/archive/2011/03/31/hosting-simple-nuget-package-feed.aspx
  [2]: http://www.hanselman.com/blog/HowToAccessNuGetWhenNuGetorgIsDownOrYoureOnAPlane.aspx
  [3]: http://docs.nuget.org/docs/reference/nuspec-reference#Specifying_Dependencies_in_version_2.0_and_above
  [4]: https://stackoverflow.com/questions/12819868/nuget-packaging-and-referencing-dlls
  [5]: http://www.xavierdecoster.com/post/2012/04/27/install-package-nuspec-aspx
  [6]: https://stackoverflow.com/questions/9180904/automating-creating-nuget-package-as-part-of-build-process
  [7]: https://stackoverflow.com/questions/14982266/the-replacement-token-description-has-no-value

Build NuGet Package automatically including referenced dependencies

New to C# programming, I&#39;d like to be able to access `MySQL` Databases. &lt;br/&gt; 

I know `MySQL connector/NET` and `MySQL for Visual Studio` are required for C# development. &lt;br/&gt; 
Do I need to install them into my app? &lt;br/&gt; 
Is it possible I can just release the connector DLL with the program?

Update: &lt;br/&gt; 
Are both of them required for the end-user or just the connector? &lt;br/&gt; 
Is there anything else they would need?

How to connect to MySQL Database?

I have a NuGet package I created and installed in another solution but now I need to debug the code of the package when called from my new solution.

I tried referencing the solution of the package but it&#39;s not working.

I am using Visual Studio 2013.

How to debug code in NuGet package created by me

I&#39;m creating my first nuget package.  I added a dependency with a version that is not the latest version.  However, I don&#39;t want to update to the latest version of this dependency.  Is it possible to instruct it to use the specific version?

    &lt;dependencies&gt;
      &lt;dependency id=&quot;NHibernate&quot; version=&quot;3.2.0.3001&quot; /&gt;
    &lt;/dependencies&gt;

When I install the package I see this:

    Attempting to resolve dependency &#39;NHibernate (≥ 3.2.0.3001)&#39;.

This creates the following when I install the package.

    &lt;packages&gt;
      &lt;package id=&quot;Iesi.Collections&quot; version=&quot;3.2.0.4000&quot; /&gt;
      &lt;package id=&quot;NHibernate&quot; version=&quot;3.2.0.4000&quot; /&gt;
    &lt;/packages&gt;

I&#39;d really like to see something like this:
    Attempting to resolve dependency &#39;NHibernate (3.2.0.3001)&#39;.

How to specify specific dependency version in nuspec?

I have made a NuGet package that works well when I use it from a C# project. It contains a DLL in the `lib/net40` directory, and the DLL gets added as a reference.

Now that NuGet supports C++, how do I actually modify my package so that the DLL can be added as a managed reference in a C++/CLI project? I can&#39;t find any tutorials explaining this. If I try to just add the package as is, I get the following error:

&gt; You are trying to install this package into a project that targets &#39;Native,Version=v0.0&#39;, but the package does not contain any assembly references or content files that are compatible with that framework.

One would think that the solution is to put the files under lib/native, but according to http://docs.nuget.org/docs/reference/support-for-native-projects, that is not supported. Also, simply putting the DLL directly under lib doesn&#39;t seem to do anything.

Apparently, I am supposed to do this with a `.props` or `.targets` file under build/native, but what do I need to put into those files to make this work ?

How can I make my managed NuGet package support C++/CLI projects?

I want to install an older version of a package (`Newtonsoft.Json`). But NuGet rolls back:

    PM&gt; Install-Package Newtonsoft.Json -Version 4.0.5
    Successfully installed &#39;Newtonsoft.Json 4.0.5&#39;.
    Install failed. Rolling back...
    Install-Package : Already referencing a newer version of &#39;Newtonsoft.Json&#39;.

How can I do it?






How can I install an older version of a package via NuGet?

My visual studio is installed on a machine which doesn&#39;t have internet connection so I can&#39;t download and install packages from NuGet Manager in VS.  
So I am looking for a way to use another machine which has internet connection to download packages and then install on VS.


Is there a way to download packages from nuget.org then do an offline installation into Visual Studio?

Nuget packages download Javascript files to ~/Scripts

I prefer to keep my content organized in a ~/content folder, which contains

    ~/content/css
    ~/content/images
    ~/content/scripts
    ~/content/scripts/vendor (for packages/ downlaoded scripts)
    ~/content/scripts/site (my own site&#39;s JS)

How do I make Nuget download Javascript files to `~/content/scripts/vendor`?

NuGet scripts to different directory

I have a build pipeline set up to create Nuget packages and publish them to a feed in artifacts.

I was able to use the feed successfully.

However when I ran the pipeline again, causing the packages to publish again I am not able to update the consuming project successfully.

Even though I can see the correct new version number in the Package Manager (Visual Studio -&gt; Tools-&gt; Nuget Package Manager -&gt; Manage Nuget Packages for solution)

When I click install I get an error 

    Package &#39;&lt;mypackagename with version number&gt;&#39; is not found in the following primary source

    &lt;correct feed nuget/v3/index.json&gt; Please verify all your online package sources are available (OR) package id, version are specified correctly.
 



Package is not found in the following primary source

I am having trouble getting the EF to install on my very simple project called &#39;Match&#39; (just now learning MVC, better late than never).  The general context here is that I created the Model class with only 2 fields and now I want to change the Model class to have a few more fields/properties. I have made the change in the Model class and am now trying to update the DB to match. I am trying to use Update-Database from EF to do that.

&gt;PM&gt; install-package EntityFramework
You are downloading EntityFramework from Microsoft, the license agreement to which is available at http://go.microsoft.com/fwlink/?LinkId=253898&amp;clcid=0x409. Check the package for additional dependencies, which may come with their own license agreement(s). Your use of the package and dependencies constitutes your acceptance of their license agreements. If you do not accept the license agreement(s), then delete the relevant components from your device.
Successfully installed &#39;EntityFramework 5.0.0&#39;.
Successfully added &#39;EntityFramework 5.0.0&#39; to Match.

&gt;Type &#39;get-help EntityFramework&#39; to see all available Entity Framework commands.

&gt;PM&gt; Enable-Migrations
Get-Package : A parameter cannot be found that matches parameter name &#39;ProjectName&#39;.
At C:\Users\Dave\Documents\Visual Studio 2010\Projects\Match\packages\EntityFramework.5.0.0\tools\EntityFramework.psm1:611 char:40
+ $package = Get-Package -ProjectName &lt;&lt;&lt;&lt; $project.FullName | ?{ $_.Id -eq &#39;EntityFramework&#39; }
+ CategoryInfo : InvalidArgument: (:) [Get-Package], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,NuGet.PowerShell.Commands.GetPackageCommand

&gt;The EntityFramework package is not installed on project &#39;Match&#39;.



The EntityFramework package is not installed on project

I generate a nuget package from a project with this command in the post-build event. the variable `%conf%` is set to the right configuration (debug or release) and `%1` is the project name (e.g. &quot;MyCompany.MyProject&quot;).

    nuget pack -Prop Configuration=%conf% &quot;%1.csproj&quot; -exclude *.sql -IncludeReferencedProjects

This package is for our own usage only, it will never be published on nuget. It ends in our private repository.

In the project, there is a file that is set to `generate action : content` and `copy local : always`. (My Visual Studio is in French, so I&#39;m not 100% sure of the translation). Let&#39;s name it `importantfile.xml`.

In the generated package, I end up with this structure :

    - content
        - importantfile.xml
    - lib
        -net45 (.NetFramework,Version=v4.5)
            -MyCompany.MyProject.dll

Which is fine, I want `importantfile.xml` to be deployed in the package, because, well, this file is important!

When I install the package in another project, `importantfile.xml` is deployed at the root of the project. That&#39;s OK. But it is not set to `copy local : always`.

**I need `importantfile.xml` to be `copy local : always` in this project where I install my package.** 

**How can I achieve that?**

**_Notes :_**

I _can_ set `copy local : always` on the file just after installing the package, that&#39;s no big deal. I would live with it if later updates of the package would let this property as-is, which is not the case. When updating the package, `copy local` is reset to `never` (as stated [here][1]).

There&#39;s a nuspec file in the project&#39;s folder, here it is :

    &lt;?xml version=&quot;1.0&quot;?&gt;
    &lt;package &gt;
      &lt;metadata&gt;
        &lt;id&gt;$id$&lt;/id&gt;
        &lt;version&gt;$version$&lt;/version&gt;
        &lt;title&gt;$title$&lt;/title&gt;
        &lt;authors&gt;$author$&lt;/authors&gt;
        &lt;owners&gt;$author$&lt;/owners&gt;
        &lt;requireLicenseAcceptance&gt;false&lt;/requireLicenseAcceptance&gt;
        &lt;description&gt;$description$&lt;/description&gt;
        &lt;copyright&gt;Copyright 2014&lt;/copyright&gt;
        &lt;tags&gt;some random tags&lt;/tags&gt;
      &lt;/metadata&gt;
    &lt;/package&gt;


  [1]: https://nuget.codeplex.com/workitem/1854

Set content files to &quot;copy local : always&quot; in a nuget package

I upgraded Microsoft.AspNetCore from 2.0.3 to 2.0.5 and my WebAPI project, although running successfully locally, fails to start in production (IIS). Everything was fine in production until this upgrade. The error message produced in the log directory is as follows:

    Error:
      An assembly specified in the application dependencies manifest (MyProject.WebAPI.deps.json) was not found:
        package: &#39;Microsoft.AspNetCore.Mvc.Abstractions&#39;, version: &#39;2.0.2&#39;
        path: &#39;lib/netstandard2.0/Microsoft.AspNetCore.Mvc.Abstractions.dll&#39;
    
      This assembly was expected to be in the local runtime store as the application was published using the following target manifest files:
        aspnetcore-store-2.0.5.xml

Could someone explain to me the details of exactly what this means? I assume it&#39;s a version mismatch of sorts, but why is this occurring? I thought the latest stable releases of NuGet packages weren&#39;t supposed to have such issues.

I was able to resolve the issue by downgrading Microsoft.AspNetCore.All from 2.0.5 to 2.0.3, but would like to find a better solution to the issue so I can use the most up-to-date version of this package.

An assembly specified in the application dependencies manifest (...) was not found

I have an automated build process that I&#39;d like to extend so I can build the libraries I am distributing via NuGet.  Currently, running nuget.exe to create the packages is a manual operation.

**What is the best way to setup VS 2010 so that my NuGet package (*.nupkg) file is the end result of a &quot;Release&quot; build?**

Keep in mind that I have other files (content and tools) for some of the packages. And, in most cases, I have multiple projects merged into a single NuGet package to support .NET 4, Silveright and Phone 7.

*(I should clarify that the existing &quot;automated&quot; process is a simple batch-file runner that builds a solution using the command line.)*

**UPDATE**

I want to refresh this discussion because the issue has not been resolved.  While the link @pravin supplied is helpful, it doesn&#39;t address the fact that I have multiple projects in a single package as well as other contents like PowerShell scripts, configuration and source code transformations, etc.

The best example I can use is an assembly that has both a .NET 4 and Silverlight 5 version. These are distributed in the same package.  I cannot use a post-build event to create the package because the package is dependent upon TWO projects.

Automating creating NuGet package as part of build process

Does anyone know to remove a specific version of a package on a TeamCity Nuget Feed?

How to remove a specific version of a package on a TeamCity Nuget Feed?

I am using Nuget to create packages. I would like to create a package which does not contain any dependencies (in the `.nuspec`) file to any other NuGet packages. My project does have NuGet package dependencies defined in its `packages.config` file.

First I create the `.nuspec` file...

    C:\code\MySolution&gt;.nuget\nuget.exe spec MyProject\MyProject.csproj

I edit the generated `.nuspec` file to be minimal, with no dependencies.

    &lt;?xml version=&quot;1.0&quot;?&gt;
    &lt;package &gt;
      &lt;metadata&gt;
        &lt;id&gt;MyProject&lt;/id&gt;
        &lt;version&gt;1.2.3&lt;/version&gt;
        &lt;title&gt;MyProject&lt;/title&gt;
        &lt;authors&gt;Example&lt;/authors&gt;
        &lt;owners&gt;Example&lt;/owners&gt;
        &lt;requireLicenseAcceptance&gt;false&lt;/requireLicenseAcceptance&gt;
        &lt;description&gt;Example&lt;/description&gt;
        &lt;copyright&gt;Copyright 2013 Example&lt;/copyright&gt;
        &lt;tags&gt;example&lt;/tags&gt;
        &lt;dependencies /&gt;
      &lt;/metadata&gt;
    &lt;/package&gt;

Then I build the solution and create a NuGet package...

    C:\code\MySolution&gt;.nuget\nuget.exe pack MyProject\MyProject.csproj -Verbosity detailed

Here is the output of that command...

    Attempting to build package from &#39;MyProject.csproj&#39;.
    Packing files from &#39;C:\code\MySolution\MyProject\bin\Debug&#39;.
    Using &#39;MyProject.nuspec&#39; for metadata.
    Found packages.config. Using packages listed as dependencies

    Id: MyProject
    Version: 1.2.3
    Authors: Example
    Description: Example
    Tags: example
    Dependencies: Google.ProtocolBuffers (= 2.4.1.473)

    Added file &#39;lib\net40\MyProject.dll&#39;.

    Successfully created package &#39;C:\code\MySolution\MyProject.1.2.3.nupkg&#39;.

The `.nupkg` package that is created has a `.nuspec` file contained within it but it includes a dependencies section which I did not have in the original `.nuspec` file...

    &lt;dependencies&gt;
      &lt;dependency id=&quot;Google.ProtocolBuffers&quot; version=&quot;2.4.1.473&quot; /&gt;
    &lt;/dependencies&gt;

I believe this is happening because of this... (from the output above)

    Found packages.config. Using packages listed as dependencies

How can I make NuGet **not** automatically resolve dependencies and insert them into the `.nuspec` file which is generated from the `pack` command?

I am using NuGet 2.2 currently. Also, I don&#39;t think that this behaviour happened in older version of NuGet; is this a new &quot;feature&quot;? I couldn&#39;t find any documentation describing this &quot;feature&quot; or when it was implemented.

All Nuget Package Solutions on Gang of Coders

Total of 32 Nuget Package Solutions