DnnVsDebugger package

[dazinator]

For the v3.0 release I am going to make the following changes:

1. Installing the DnnPackager nuget package into a project will no longer give you any deployment or debugging capabilities. It won't give you any Powershell commands either (as they are now obsolete). It will now only contain the MsBuild tasks and targets which produce the install packages as a result of the build.

2. I will publish a seperate tool as a Chocolatey package called the "DnnVsDebugger" tool. You will need to install this package and then change some configuration in your project properties page in order to get the deployment / debugging support.

Installation of this tool will typically look like this (using chocolatey)

choco install DnnVsDebugger

Once installed, this will place the DnnVsDebugger.exe on your PATH.

Configuration of this tool for your project will look something like this (project properties page):

You will now be able to "Run" your project in VS, by pressing the play button. This will call the DnnVsDebugger.exe which will take care of the rest:

1. Deployment of the Install Packages to the specified website.
2. Detect if the website is not currently running and Ping() it to ensure it is started.
3. Attachment of your VS debugger to the website process
4. Launching the browser at the URL you have specified (you can control this via arguments)

I feel that by seperating out the VS logic into a seperate package, it paves the way for other support packages for other types of IDE's potentially in the future. DnnPackager nuget package can stay simple and only need concern itself with MsBuild logic to produce install packages.