VS Code Debugging Improvements

[JohnCampionJr]

This took some work but I feel like I created a real smooth developer experience for debugging both Vue and NET Core in VS Code.

I added a bit of code to the startup of the template to allow for a few arguments to be passed.

The vue-cli server mode can be passed.
Start mode is the same way it is usually done, with the C# Configure starting the NPM runner and attaching to it.
Attach mode is just attaching to an existing VueCli Server

A port parameter can be passed to make it easy to use different ports if needed.

Lastly, a kill parameter uses the same code in VueCliMiddleware to shut down any stray Vue Cli processes (I was having them get stuck kind of regularly).

Then, I completely reworked the launch and task files for VS Code. I really didn't like not being able to see the Vue Cli server launched in the background by the VueCliMiddleware

The .NET Core & Vue Server is what I'm most proudest of :)
It does this:

• Builds C# project
• After that completes, it launches the VueCli in a separate terminal (with the progress showing its build)
• After that succeeds, it launches the C# project for debugging
• Finally, it launches the Chrome task to start the Vue debugging.

You can see everything that's happening and it all happens in sequence.

The .NET Core Web launch config is similar to the original except I changed it to launch the Chrome debug config.

On both, I set it to turn off the numerous module load messages in the debug console.

So with one launch command, I get this

[liborpansky]

I've just tested the new debug experience and looks pretty good! Well done