Project as blacklist manifest

Sep 5, 2014 at 9:11 PM
Edited Sep 5, 2014 at 9:23 PM
I was wondering if it could be possible to have the project use blacklisting behavior rather than whitelisting behavior in its manifest. Our team is switching back and forth between Visual Studio and WebStorm and any time someone creates a new .js file or moves a .js file the Visual Studio project's manifest has to be manually updated. I'd rather choose to exclude specific files and folders instead.

I know there's a "web site" option as an alternative to a "web project" that sort of works this way, but my frustration with "web site" is that it becomes an absolute hard drive path reference for a specific user and as such cannot declare the project root relative to the solution. Each developer on the team has a different container directory structure for containing the solution.

EDIT: I took a stab at actually using the website option but it also uses a whitelisting manifest....
Coordinator
Sep 10, 2014 at 8:52 PM
Hi stimpy77,

I'm curious as to what scenario requires you to add the files to the project? Most functionality should work just as well if the files are not included in the project (that's what we aim for).
Sep 10, 2014 at 9:13 PM
Uhh how about the ability to see and edit the files in the IDE without enabling "Show All Files" and seeing the files all ghosted-out?
Coordinator
Sep 11, 2014 at 10:28 PM
Show All Files is enabled by default for node.js projects. You should be able to open the files even if they look ghosted-out, and get IntelliSense just as well as if they were included in the project.

It's not ideal, but it's a compromise we have to make in order to get a v1 released.

ASP.NET is moving in that direction for Dev14, so hopefully we can take advantage of their work at some point.
Marked as answer by crwilcox on 9/23/2014 at 10:28 AM