SSDT Installation for VS2017 Team Explorer Fails

Question

I am attempting to install SSDT v15.6.0 into an existing Visual Studio Team Explorer 2017 instance. When I run the SSDT installer, I can select Visual Studio Team Explorer 2017

Answer 1

This is how I fixed it :

1. Run installer normally to the end and let it fail.
2. When it fails the window will have a link to the log file, open it.
3. In this log file, 1 or 2 lines before the error(Process returned error: 0x80131500) problem component location will be revealed, something like this:

[6748:674C][2020-07-29T09:44:03]i301: Applying execute package: ISVsix, action: Install, path: C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe" /q /admin /instanceIds:"5403e431" /logFile:"C:\Users\xxxx\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200729093525_11_ISVsix.log" "payload\Microsoft.DataTools.IntegrationServices.vsix"

You have to combine location of the VSIXBootstrapper with vsix component location. In my case I had vsix file under C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\payload

4. Copy failing component(.vsix), in this case Microsoft.DataTools.IntegrationServices.vsix to some folder before it gets deleted. If it already got deleted then restart the installer and search for this component in parent folders.
5. Restart your computer. I was getting "Another installation running .." error before I did.
6. Go to the folder where you copied the failing component and install the .vsix manually. This time it should install normally.
7. Repeat step 1 but this time hoping it will work normally.

I hope this at least gets you in the right direction.

Answer 2

This is currently broken due to a bug in Visual Studio - see this post on the Developer Community site: SSDT cannot install onto 15.7 version of Visual Studio

It'll be fixed in a forthcoming Visual Studio update, but if you can't wait for that a workaround is to completely uninstall Visual Studio and install an older version. See my answer here for instructions: https://stackoverflow.com/a/50349464/1184850

Answer 3

With the release of SSDT 15.7.1, Team Explorer no longer shows up as an existing Visual Studio install instance option within SSDT. At first I was concerned that the SSDT install would install a Visual Studio shell with no TFS connectivity, however this was not the case. It appears that the SSDT install of the Visual Studio shell picks up on the fact that Visual Studio Team Explorer 2017 is already installed on the machine and the SSDT Visual Studio shell instance has full TFS Connectivity!