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....
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....