search

aspnet / Tooling

Issue tracker and info on Visual Studio tooling for ASP.NET
Other
256 stars 124 forks source link

No project.json intellisense in dependencies node when no frameworks are specified #207

Open danroth27 opened 9 years ago

danroth27 commented 9 years ago

I built up a quick DNX project by hand for a project I am working on and I didn't bother to add the frameworks node. Without the frameworks node I don't get any intellisense for the dependencies node. We should still provide intellisense for dependencies even when no frameworks are specified. We could either honor the default framework used by DNX (currently dnx451) or we could just list all packages without any filters.

sayedihashimi commented 9 years ago

TFS:150841 I've added it to our internal TFS tracker, we will reply back here soon.

webtools-bot commented 7 years ago

The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.

If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.

By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.

Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!