Skip to content
This repository has been archived by the owner on Sep 13, 2022. It is now read-only.

Installing a package using NuGet does not create packages folder for .Net framework 4.6.2 #433

Closed
goelankita opened this issue Jul 26, 2017 · 2 comments

Comments

@goelankita
Copy link

I am creating a console app using Visual Studio 2017 and selecting .Net framework 4.6.2. When I install any library package using NuGet, it is not creating Packages folder on solution level. But when I do the same using .Net framework 4.5.2, it creates packages folder

@weshaggard
Copy link
Member

@emgarten any thoughts?

@emgarten
Copy link
Member

emgarten commented Aug 4, 2017

Projects using packages.config will create a solution level packages folder.

Projects using PackageReference items in the csproj use a global packages folder and create a an obj\project.assets.json file to reference the packages.

It sounds like the net 4.5.2 project may have been created using packages.config. The net 4.6.2 project is likely a ".NET Core" project using PackageReference.

Take a look at the csproj files to find out for sure.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants