Per project: References-&gt;Nuget dictates what packages are referenced and restored. But, as Eastrall mentioned, the packages folder is now global and located in your user folder: `C:\Users\[YourUsername]\.nuget\packages`

&lt;h2&gt;To force ./packages folder for Solution&lt;/h2&gt;

To force download of packages folder to be a child of the solution folder for .NET Core projects, follow these steps:

  1. Create a `NuGet.Config` file in the same directory as the `.sln` file.

  2. Copy the following contents into the  `NuGet.Config` file:

&gt;     &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
&gt;     &lt;configuration&gt;
&gt;       &lt;config&gt;
&gt;         &lt;add key=&quot;globalPackagesFolder&quot; value=&quot;.\packages&quot; /&gt;
&gt;       &lt;/config&gt;
&gt;     &lt;/configuration&gt;

  3. Configure NuGet to download missing packages by:

  3.1. In Visual Studio: `Tools -&gt; Options`

  3.2. Filter by `nuget` (top left in dialog). Select `General`

  3.3. Ensure `Allow NuGet to download missing packages` is checked

[![enter image description here][1]][1]

  3. Close and re-open the solution. NuGet will download the required packages.


___

Note: the NuGet.Config configuration can also be achieved by executing the following command from the NuGet Package Manager Console (`Tools -&gt; NuGet Package Manager -&gt; Package Manager Console`):

    PM&gt; nuget config -set globalPackagesFolder=.\packages -configfile &quot;$(pwd)\NuGet.Config&quot;


  [1]: https://i.stack.imgur.com/Qq5Hl.png





You still have `packages` folder in your .NET Core solution, but the global packages are located at: `C:\Users\[YourUsername]\.nuget\packages`



You can check out a question I asked to see if the answers do you any good.

https://stackoverflow.com/questions/43687058/how-do-i-include-nuget-packages-in-my-solution-for-net-core-projects

You can get that packages folder back, but you might not be happy with the results, since .Net Core projects rely on so many NuGet packages.  Mine is hovering around 1 GB.

https://docs.microsoft.com/en-us/nuget/schema/nuget-config-file#config-section


I am familiar w/ loading an appsettings.json section into a strongly typed object in .NET Core startup.cs. For example:

    public class CustomSection 
    {
       public int A {get;set;}
       public int B {get;set;}
    }

    //In Startup.cs
    services.Configure&lt;CustomSection&gt;(Configuration.GetSection(&quot;CustomSection&quot;));
    
    //Inject an IOptions instance
    public HomeController(IOptions&lt;CustomSection&gt; options) 
    {
        var settings = options.Value;
    }

I have an appsettings.json section who&#39;s key/value pairs will vary in number and name over time. Therefore, it&#39;s not practical to hard code property names in a class since new key/value pairs would require a code change in the class. A small sample of some key/value pairs:

    &quot;MobileConfigInfo&quot;: {
        &quot;appointment-confirmed&quot;: &quot;We&#39;ve booked your appointment. See you soon!&quot;,
        &quot;appointments-book&quot;: &quot;New Appointment&quot;,
        &quot;appointments-null&quot;: &quot;We could not locate any upcoming appointments for you.&quot;,
        &quot;availability-null&quot;: &quot;Sorry, there are no available times on this date. Please try another.&quot;
    }

Is there a way to load this data into a MobileConfigInfo Dictionary&lt;string,string&gt; object and then use the IOptions pattern to inject MobileConfigInfo into a controller?


How to load appsetting.json section into Dictionary in .NET Core?

How can I generate patch for all commits in a given branch by knowing only the branch name?

This step is part of a complex workflow all of which is being automated.  Hence requiring someone to manually determine the first commit in the branch is not an option.

Note that anything relying on reflog is not an option either because changes in the branch are not made locally.

How to generate patch for all commits in a branch?

Are packages now cached in a more shared location somewhere or what?

My solution folder is devoid of any `packages` folder:

[![Solution folder without packages folder][1]][1]

  [1]: https://i.stack.imgur.com/cDAkD.png


Why isn&#39;t there any packages folder in my .NET Core solution&#39;s containing folder?

Are packages now cached in a more shared location somewhere or what?
My solution folder is devoid of any <code>packages</code> folder:
<a href="https://i.stack.imgur.com/cDAkD.png" target="_blank" rel="noopener noreferrer"><img src="https://i.stack.imgur.com/cDAkD.png" alt="Solution folder without packages folder"></a>

Suppose I have a class library which I want to target netstandard1.3, but also use `BigInteger`. Here&#39;s a trivial example - the sole source file is `Adder.cs`:

&lt;!-- language: c# --&gt;

    using System;
    using System.Numerics;
    
    namespace Calculator
    {
        public class Adder
        {
            public static BigInteger Add(int x, int y)
                =&gt; new BigInteger(x) + new BigInteger(y);            
        }
    }

Back in the world of `project.json`, I would target `netstandard1.3` in the `frameworks` section, and have an explicit dependency on `System.Runtime.Numerics`, e.g. version 4.0.1. The nuget package I create will list just that dependency.

In the brave new world of csproj-based dotnet tooling (I&#39;m using v1.0.1 of the command-line tools) there&#39;s an [implicit metapackage package reference](https://github.com/dotnet/core/blob/master/release-notes/1.0/sdk/1.0-rc3-implicit-package-refs.md) to `NETStandard.Library 1.6.1` when targeting `netstandard1.3`. This means that my project file is really small, because it doesn&#39;t need the explicit dependency:

&lt;!-- language: xml --&gt;

    &lt;Project Sdk=&quot;Microsoft.NET.Sdk&quot;&gt;
      &lt;PropertyGroup&gt;
        &lt;TargetFramework&gt;netstandard1.3&lt;/TargetFramework&gt;
      &lt;/PropertyGroup&gt;
    &lt;/Project&gt;

... but the nuget package produced has a dependency on `NETStandard.Library`, which suggests that in order to use my small library, you need *everything* there.

It turns out I can disable that functionality using `DisableImplicitFrameworkReferences`, then add in the dependency manually again:

&lt;!-- language: xml --&gt;

    &lt;Project Sdk=&quot;Microsoft.NET.Sdk&quot;&gt;    
      &lt;PropertyGroup&gt;
        &lt;TargetFramework&gt;netstandard1.3&lt;/TargetFramework&gt;
        &lt;DisableImplicitFrameworkReferences&gt;true&lt;/DisableImplicitFrameworkReferences&gt;
      &lt;/PropertyGroup&gt;
      
      &lt;ItemGroup&gt;
        &lt;PackageReference Include=&quot;System.Runtime.Numerics&quot; Version=&quot;4.0.1&quot; /&gt;
      &lt;/ItemGroup&gt;    
    &lt;/Project&gt;

Now my NuGet package says exactly what it depends on. Intuitively, this feels like a &quot;leaner&quot; package.

So what&#39;s the exact difference for a consumer of my library? If someone tries to use it in a UWP application, does the second, &quot;trimmed&quot; form of dependencies mean that the resulting application will be smaller?

By not documenting `DisableImplicitFrameworkReferences` clearly (as far as I&#39;ve seen; I read about it [in an issue][1]) and by making the implicit dependency the default when creating a project, Microsoft are *encouraging* users to just depend on the metapackage - but how can I be sure that doesn&#39;t have disadvantages when I&#39;m producing a class library package?

  [1]: https://github.com/dotnet/sdk/issues/764

What are the application implications of a netstandard library depending on a metapackage?

I edit the project.csproj. and re-open the solution the errors occurred:
The operation failed as details for project xxx could not be loaded

I try delete  obj &amp; bin folder, clear the nuget cache by tool&gt;options. 
but the error still exist.

Remark: the error do not occur each time, i just restart the project  three times. the first and second is correct. but the third the error occur

vs2017:
Microsoft Visual Studio Community 2017
Version 15.0.26228.9 D15RTWSVC
Microsoft .NET Framework
Version 4.6.01586

Package Manager Console Host Version 4.0.0.2323



VS2017 The operation failed as details for project could not be loaded

I want to create a NuGet package which adds multiple .dll files as references to my project.

I have a folder with 10 .dlls files in it. 

When I install this via nuget, I want these files to be added to the project&#39;s references.

Create nuget package from dlls

Using the `dotnet` command line tool, how can I add a reference to an existing local package that is *not* downloaded with NuGet?

I have tried adding a local package to a project `bar` with `dotnet`:

```lang-none
dotnet add package /Users/sakra/foo/bin/Debug/foo.1.0.0.nupkg
```

The package `foo.1.0.0.nupkg` has been created with `dotnet pack` in a different project. The command `dotnet add package` however tries to download the file `foo.1.0.0.nupkg` from https://api.nuget.org/ which of course fails.


Add a package with a local package file in &#39;dotnet&#39;

I&#39;m trying to write a plugin system with .NET Core, and one of my requirements are to be able to distribute the plugin DLL along with its dependencies to the user for install.

However, I can&#39;t figure out how to include my NuGet dependencies as a build artifact and have them output to the build folder, without having to use `dotnet publish` as a hack. Is there some way I can specify this in the .csproj file (project file)?


How do I get .NET Core projects to copy NuGet references to the build output?

I have asp.net core application. I want to use `IOptions` pattern to inject values from appsettings.json. So I have a class `SecurityHeaderOptions`, and also have target class `SecurityHeadersBuilder` whose constructor takes `IOptions&lt;SecurityHeaderOptions&gt;` as parameter.

I know that .net core can implicitly create instance of `SecurityHeadersBuilder` by injecting `IOptions&lt;SecurityHeaderOptions&gt;` after registering both with container.

However i want to explicitly create instance of `SecurityHeadersBuilder`, call one of its method and then register the instance with the container.


```csharp
public sealed class SecurityHeaderOptions
{
	public string FrameOption { get; set; }    
	public string XssProtection { get; set; }
}


public class SecurityHeadersBuilder
{
	private readonly SecurityHeaderOptions _options = null;

	public SecurityHeadersBuilder(IOptions&lt;SecurityHeaderOptions&gt; options)
	{
		_options = options.Value;    
	}

	public SecurityHeadersBuilder AddDefaultPolicy()
	{
		AddFrameOptions();
		AddConetntSecurityPolicy();
		return this;
	}
}
```


**ConfigureServices method**

```csharp
public void ConfigureServices(IServiceCollection services)
{        
	services.Configure&lt;SecurityHeaderOptions&gt;(Configuration.GetSection(&quot;SecurityHeaderOptions&quot;));

	services.AddScoped&lt;SecurityHeadersBuilder&gt;(provider =&gt; 
		   new SecurityHeadersBuilder(?????).AddDefaultPolicy())
}
```

**Questions**  
1&gt; If i am explicitly passing options into constructor, do i need to register `SecurityHeaderOptions` with the container using `service.Configure` method?     

2&gt; `Configuration.GetSection(&quot;SecurityHeaderOptions&quot;)` can&#39;t return instance of `IOptions&lt;SecurityHeaderOptions&gt;` , instead it returns `IConfigurationSection`?

3&gt;Either way, how do I retrieve and pass `SecurityHeaderOptions` into `SecurityHeadersBuilder`&#39;s constructor?

How to get IOptions in ConfigureServices method?

In Visual Studio, there are at least three different types of class libraries you can create:

* Class Library (.NET Framework)
* Class Library (.NET Standard)
* Class Library (.NET Core)

While the first is what we&#39;ve been using for years, a major point of confusion I&#39;ve been having is when to use the .NET Standard and .NET Core class library types. I&#39;ve been bitten by this recently when attempting to [multi-target different framework versions][1], and [creating a unit test project][2].

So, what is the difference between *Class Library (.NET Standard)* and *Class Library (.NET Core)*, why do both exist, and when should we use one over the other?

  [1]: https://stackoverflow.com/a/42748869/983064
  [2]: https://stackoverflow.com/questions/42938879/cant-get-xunit-tests-to-run-with-net-core


What is the difference between .NET Core and .NET Standard Class Library project types?

I have spent the better part of a few hours trying to find a way to auto-increment versions in a .NETCoreApp 1.1 (Visual Studio 2017).

I know the the AssemblyInfo.cs is being created dynamically in the folder: ```obj/Debug/netcoreapp1.1/```

It does not accept the old method of: 
```[assembly: System.Reflection.AssemblyFileVersionAttribute(&quot;1.0.0.*&quot;)]```

If I set the project to package I can set versions there but this seems to be used to build the AssemblyInfo.cs file.

My question is, has anyone figured out how to control version in .NET Core (or .NETStandard for that matter) projects.

Auto Versioning in Visual Studio 2017 (.NET Core)

All of a sudden, I am getting the following errors for 3 projects in a solution:

    Error NU1105 Unable to find project information for &#39;C:\code\example\src\libs\example.I18n\example.I18n.csproj&#39;. 
    The project file may be invalid or missing targets required for restore.

The only thing that has changed in the project is a couple of DB changes, but I never had any issues in the past. The only other thing is that I updated to Visual Studio 2017 15.5. Could that cause issues?

I have tried removing and recloning the solution from source control, but still getting errors. No problems on my colleagues&#39; machines, so it must be something local.

Example of one of the .csproj files if this helps:

&lt;!-- language: lang-xml --&gt;

    &lt;Project Sdk=&quot;Microsoft.NET.Sdk&quot;&gt;
    
      &lt;PropertyGroup&gt;
        &lt;TargetFramework&gt;net452&lt;/TargetFramework&gt;
        &lt;AssemblyName&gt;Example.I18n&lt;/AssemblyName&gt;
        &lt;PackageId&gt;Example.I18n&lt;/PackageId&gt;
        &lt;GenerateAssemblyConfigurationAttribute&gt;false&lt;/GenerateAssemblyConfigurationAttribute&gt;
        &lt;GenerateAssemblyCompanyAttribute&gt;false&lt;/GenerateAssemblyCompanyAttribute&gt;
        &lt;GenerateAssemblyProductAttribute&gt;false&lt;/GenerateAssemblyProductAttribute&gt;
      &lt;/PropertyGroup&gt;
    
      &lt;ItemGroup&gt;
        &lt;PackageReference Include=&quot;Microsoft.AspNetCore.Mvc.Core&quot; Version=&quot;1.1.2&quot; /&gt;
        &lt;PackageReference Include=&quot;Microsoft.Extensions.Logging&quot; Version=&quot;1.1.1&quot; /&gt;
        &lt;PackageReference Include=&quot;MessageFormat&quot; Version=&quot;1.0.1&quot; /&gt;
      &lt;/ItemGroup&gt;
    
      &lt;ItemGroup Condition=&quot; &#39;$(TargetFramework)&#39; == &#39;net452&#39; &quot;&gt;
        &lt;Reference Include=&quot;System&quot; /&gt;
        &lt;Reference Include=&quot;Microsoft.CSharp&quot; /&gt;
      &lt;/ItemGroup&gt;
    
    &lt;/Project&gt;


Error NU1105 Unable to find project information - The project file may be invalid or missing targets required for restore

I&#39;m trying to use nopCommerce(Which is written in .NET Core) but when I want to run the project I face 52 Errors telling me Run a nuget package restore 

&gt; Assets file ~\obj\project.**assets.json&#39;** not found. Run a NuGet package restore to generate this file.	Nop.Web.MVC.Testsote
 

when I use the right click on the solution and selecting Restore Nuget Packages I get this message:  
&gt; All packages are already installed and there is nothing to restore.

but those 52 Errors are still there and in ***Tools -&gt; NuGet Package Manager -&gt; Manage NuGet Packages for Solution***  there is nothing installed on the solution,also I Recently updated my VS2017 to 15.5.4



Content Type	Original Author	Original Content on Stackoverflow
Question	ProfK	View Question on Stackoverflow
Solution 1 - Nuget	MSC	View Answer on Stackoverflow
Solution 2 - Nuget	CJBS	View Answer on Stackoverflow
Solution 3 - Nuget	Eastrall	View Answer on Stackoverflow
Solution 4 - Nuget	Eric	View Answer on Stackoverflow

Why isn't there any packages folder in my .NET Core solution's containing folder?

Nuget Problem Overview

Nuget Solutions

Solution 1 - Nuget

Solution 2 - Nuget

To force ./packages folder for Solution

Solution 3 - Nuget

Solution 4 - Nuget

How to generate patch for all commits in a branch?

How to load appsetting.json section into Dictionary in .NET Core?

Attributions