search

NuGet / Home

Repo for NuGet Client issues
Other
1.5k stars 252 forks source link

Cannot install packages in Node.js project - Project "Default" is not found #2145

Open maartenba opened 8 years ago

maartenba commented 8 years ago

From @chojrak11 on February 21, 2016 22:53

I have Visual Studio 2015 Update 1, with Node.js Tools for Visual Studio v1.1. Everything up to date. I have a single Node.js project in a solution. The project was created from template "Blank Node.js Web Application." I cannot install any package through Package Management Console. I need for example AngularJS.Intellisense. No luck. The message is: 'Project "Default" is not found.' In fact, the "Default Project" drop down in PMC is empty and I cannot select anything (the list is empty as well). How can I install this AngularJS.Intellisense package in my project?

Copied from original issue: NuGet/NuGetGallery#2898

yishaigalatzer commented 8 years ago
  1. Can you try saving your project and solution first?
  2. This may be solved in 3.4 (to be released with Update II), otherwise we don't plan to invest in node.js projects in one of the immediate releases.
Hermholtz commented 8 years ago
  1. Of course the solution is saved.
  2. I think it's just a kind of filter that prevents a Node.js project to be included in the drop down in Packet Management Console and selected as the default. No major work IMO to fix this feature.
zhili1208 commented 8 years ago

Installed Node.js tools for visual studio, try to open UI, got "this project is unsupported". I don't think nuget support node.js project, npm is the right solution for package management for node.js project.

yishaigalatzer commented 8 years ago

Thanks @zhili1208 for investigating.

If someone from the Node.JS team is interested in building this feature in NuGet we will take a pull request. I can't see why would someone use javascript packages from NuGet for this kind of project, but I could see someone using msbuild targets and the like.

mousetraps commented 8 years ago

Node Tools dev here - we also have an issue open from our end on this and haven't seen sufficient reason to prioritize NuGet support. Of course, we wouldn't oppose someone making a PR on NuGet :stuck_out_tongue_winking_eye: https://github.com/Microsoft/nodejstools/issues/326

Hermholtz commented 8 years ago

@zhili1208 @yishaigalatzer then maybe just please add a proper warning to NuGet when it encounters these unsupported project types, rather than obscure "No Default project" confusing stuff.

yishaigalatzer commented 8 years ago

Can we follow up on the state of this for RTM?