Add a new directory-based solution or project type
Visual Studio should support opening a directory and working with 'directory-based' projects using actual files on disk (no solution/project files, but instead Visual Studio can store project settings inside '.vs' hidden folder, similar to .idea in WebStorm / ItelliJ). The existing Website project type is not an option!
Visual Studio should support working with existing directory structures widely used in the front-end community. See project templates like 'angular-seed' or templates in 'yeoman' gallery. Developers should be able to work comfortably with these directory structures and actual files on disk, without any tweaks. Also it should have a first-class console window inside Visual Studio, something better than NuGet Package Manager Console. This console should allow developers work comfortably with git, npm, grunt, gulp, bower and similar node.js tools, ideally powered by PowerShell+PoshGit, in providing access to all the tools mentioned above and other commonly used shell tools.
The luck of this feature forces front-end developers work in other IDEs (like WebStorm).
Danny Tuppeny commented
I would really love to see this; I've wrestled with both the MPF sample, and the undocumented-CPS lately to try and implement a Dart project type, and given up in frustration :(
Here is a typical front-end project template:
Try to work with it from Visual Studio and from WebStorm. It will be obvious which features VS projects do currently miss.
Mads Kristensen commented
Have you tried the Grunt Launcher extension for VS? http://visualstudiogallery.msdn.microsoft.com/dcbc5325-79ef-4b72-960e-0a51ee33a0ff
A few problems with Website project type:
- It adds a suffix to project name, something like "App(22)", no way to rename it.
- It doesn't have npm / bower / grunt tooling (similar how you manage NuGet packages in C# projects)
- No way to define where you have source code, tests etc, which 3rd party libraries should be available as references (for IntelliSence) in which parts of your code.
- Website project settings are completely irrelevant for typical front-end apps (see yeoman templates)
For complete list of features which would be nice to have in Visual Studio see WebStorm IDE, which is currently better suited for working on front-end projects.