Reserved script name appearing under "Custom" node

Installed product versions

Visual Studio: 2015 Update 2 Enterprise
This extension: 1.3.62
Description

When both a preuninstall and a postuninstall script are defined in the scripts section of package.json, my preversion script appears under the "Custom" node in TRX.

Steps to recreate

Create a new ASP.NET app with a package.json file.
Add the following scripts to package.json:

  "scripts": {
    "foo": "echo foo",
    "preuninstall": "echo preuninstall",
    "postuninstall": "echo postuninstall",
    "preversion": "echo preversion"
  }

Current behavior

The following screenshot depicts the current behavior:

before_fix

Since version is a reserved npm script name, the preversion script should appear under the "Defaults" node in TRX. An exception is being thrown and swallowed by the catch block in the LoadTasks method of TaskParser.cs. The exception is caused by adding the "uninstall" key to a List twice.

Expected behavior

The preversion script should appear under a read-only version node within TRX's "Defaults" node:

after_fix

madskristensen / NpmTaskRunner