Commented Unassigned: Crash with Solution Explorer context menu when AWS Tools for Windows Installed: throws NotImplementedException [581]

Occurs only if Amazon’s AWS toolkit (AWS Tools for Windows 3.5.66.0) is installed since stack trace ploughs through a load of their code, which makes me suspicious. Problem happens if context menu brought up on multiselected items under npm node.

To reproduce:

1. Create a new Node.js Console Application project.
2. Edit package.json and paste in the following.

```
{
"name": "angular-app-server",
"description": "Back end server to support our angular app",
"version": "0.0.1",
"private": true,
"dependencies": {
"express": "~3.0",
"passport": "~0.1.12",
"express-namespace": "~0.1.1",
"open": "0.0.3",
"request": "~2.16.6"
},
"devDependencies": {
"rewire": "~1.0.3",
"supervisor": "~0.4.1",
"grunt": "~0.4",
"grunt-contrib-jshint": "~0.2.0",
"grunt-contrib-nodeunit": "~0.1.2"
}
}
```

3. Save package.json.
4. Right-click the npm node and click Install Missing npm Modules.
5. Wait for Visual Studio to finish updating hierarchy.
6. Select multiple npm packages under the npm node.
7. Right-click the selection.


A NotImplementedException is thrown with the following stack trace:

at Microsoft.VisualStudioTools.Project.ProjectNode.NodeFromItemId(UInt32 itemId) in c:\GitWork\rgnpm01\Common\Product\SharedProject\ProjectNode.cs:line 3469
at Microsoft.VisualStudioTools.Project.ProjectNode.GetProperty(UInt32 itemId, Int32 propId, Object& propVal) in c:\GitWork\rgnpm01\Common\Product\SharedProject\ProjectNode.cs:line 6233

Comments: Turns out this has nothing to do with the npm node. I'm guessing it would happen if you multiselected anything and then tried to bring up the context menu. For example, in Solution Explorer I just selected: - app.js - package.json - README.md I then right-clicked to bring up the context menu and got exactly the same exception, which brings down Visual Studio.