Additional VSCode support?

[Nysosis]

I notice we've got a couple of vscode specific files in the repo (launch.json and settings.json). Being an avid vscode user I'm all for it!

However the one that keeps tripping me up is no tasks.json, to run build/test via ctrl+b or ctrl+t.

Is that something we should consider putting in, if there's already support in there for other features of vscode why not more. Or really should we not make the repo editor specific like that - if we cater to the vscode crowd, why not atom or vim (I've never used them, but I presume there to potentially be some form of configuration files they support), instead remove the existing files, and leave it up to the user to decide how they want to setup their editor integration (we could have example files in the wiki or something instead).

[jamesadarich]

Hey @Nysosis, think this is a great addition and will certainly be useful when developing Alsatian. I think it'd be nice to first understand what tasks and features we'd want to have. Then we can move on to deciding which IDEs to support or whether to add info to the wiki :).

So what tasks would you suggest away from those you already have?

[Nysosis]

The only tasks I generally use in most projects I work on are some form of build, test and lint task, along with any associated problem matchers where appropriate (to make it easier to jump to the files causing issues).

All other things are one-off runs (i.e. review code), or should be handled by a CI server (i.e. publishing), so don't need to go out of the way to support (to me anyway)