Not really a bug but a potential improvement :)
When trying to install a package that has the minClientVersion unsatisfied, the dialog shows a "upgrade nuget" button. Clicking the button shows the extension manager with the intent of updating the nuget extension.
__expected behavior__
The extensions manager shows the updates tab
__actual behavior__
The extensions manager shows the installed tab
Comments: Oh, so obvious that I didn't even think of that :( Thx for the hint! However, I guess I'll need to compile the vsix myself in debug mode as the debugger complains about optimizations and no debug information when attaching to the main VS instance with the 2.5 pre-release installed. I'll give it a shot.
When trying to install a package that has the minClientVersion unsatisfied, the dialog shows a "upgrade nuget" button. Clicking the button shows the extension manager with the intent of updating the nuget extension.
__expected behavior__
The extensions manager shows the updates tab
__actual behavior__
The extensions manager shows the installed tab
Comments: Oh, so obvious that I didn't even think of that :( Thx for the hint! However, I guess I'll need to compile the vsix myself in debug mode as the debugger complains about optimizations and no debug information when attaching to the main VS instance with the 2.5 pre-release installed. I'll give it a shot.