NuGet won't install on VS 2015 Integrated Shell

[conioh]

Details about Problem

NuGet product used: NuGet Package Manager for Visual Studio 2015

NuGet version: 3.4.4.1321

VS version: 2015 Integrated Shell

OS version: Windows 10 x64 v1709 (16299.192)

Worked before? If so, with which NuGet version: Worked way back. Don't remember version

Detailed repro steps so we can see the same problem

1. Get a machine (or a VM) without Visual Studio.

2. Install Visual Studio 2015 Integrated Shell or any product that has Visual Studio 2015 Integrated Shell bundled with it.

   1. Find vs_isoshell.exe and vs_intshelladditional.exe in your old downloads directory or whatever and install them in that order. Or:
   2. Install RemObjects Elements 10 for Windows

3. Search the Nuget Package Manager extension from within the VS GUI. Fail

4. Download the extension from the VS Marketplace.

5. Try to install it.

6. Be informed that there are no compatible products install.

7. Recall that it used to work.

8. Get on GitHub and see that...

Though it's hard to follow the million renames/moves the .vsixmanifest files went through, the manifests in the old repo include the IntegratedShell ID.

After all the renames and moves, the current head includes 3 files:

• source.extension.vs14.vsixmanifest which declares support for Community, Pro and Express editions of VS 2015.
• source.extension.vs15.vsixmanifest which declares support for Community, Pro and Express editions of VS 2017. This doesn't makes a lot of sense since most of the Express editions don't have a 2017 version - there's only VS 2017 Express for Windows Desktop. No Web. No Windows 10. No Windows Phone.

and:

• source.extension.vs15.insertable.vsixmanifest which declares support for Microsoft.VisualStudio.IntegratedShell with Version="[15.0,16.0)". But there's no VS 2017 Shell! It says so everywhere. For example:

Microsoft offers the Integrated and Isolated Shells only for Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010. It is not available for Visual Studio 2017.

https://vspartner.com/pages/vsshells

It is known.

My guess is that somehow along the way someone just bumped up all the versions, even though it makes no sense. VS 2017 Integrated Shell is not a thing. VS 2015 Integrated Shell certainly is, but NuGet won't work with it.

Maybe my guess is wrong. I don't know what "insertable" even means and I couldn't even get the 2015 extension to build from the current head so I'm coming here.

It's worth noting that the VS2013 NuGet extension still works on VS 2013 Integrated Shell.

Please make the NuGet extensions work with VS 2015 Integrated Shell.

[conioh]

Hello?

[conioh]

If I take the https://github.com/NuGet/NuGet.Client/tree/3.4.4-rtm tag (since the version in the Visual Studio Marketplace is 3.4.4.1321) I can build it and if I apply the

--- a/src/NuGet.Clients/VsExtension/source.extension.vsixmanifest
+++ b/src/NuGet.Clients/VsExtension/source.extension.vsixmanifest
@@ -14,6 +14,7 @@
     <InstallationTarget Id="Microsoft.VisualStudio.VPDExpress" Version="[14.0,15.0)" />
     <InstallationTarget Id="Microsoft.VisualStudio.VSWinExpress" Version="[14.0,15.0)" />
     <InstallationTarget Id="Microsoft.VisualStudio.VSWinDesktopExpress" Version="[14.0,15.0)" />
+    <InstallationTarget Id="Microsoft.VisualStudio.IntegratedShell" Version="[14.0,15.0)" />
   </Installation>
   <Assets>

patch it installs on Visual Studio 2015 Integrated Shell too. Surprising.

If I download the VSIX from the marketplace, edit the manifest and repackage it, it works too (though mentioning the digital signature is obviously invalid):

So, is there a reason you dropped support for the shell in 2015? Can you bring it back?

[anchal288]

any fix for this issue? i need nuget on 2015 shell to code the integration with powerBI. appreciate any help with the solution/workaround.

[conioh]

@anchal288, seems like Microsoft - once again - doesn't even bother to look at bug reports. Last time they ignored bug reports they deleted many Terabytes if not Petabytes of users' files. If you really need the functionality and can't use VS Community because if the license, I'd suggest doing what I described earlier.

[conioh]

Ola?

[conioh]

Lame.

[ghost]

Issue is missing Type label, remember to add a Type label