Geek Answers Handbook

Visual Studio 2017 is not detected by installation extensions

I am trying to install an extension that is only supported on Visual Studio 2017. I am using Professional and I have never had RC, only RTM version. However, VS 2017 was not detected (see Installation Log below). Other extensions install just fine, apparently because they also support VS 2015 that I installed. These extensions appear in 2015 and 2017.

I tried installing the repair, then completely uninstalled and reinstalled it, but nothing fixed the problem. The specific extension of Roslynator 2017 .

How can I fix this so that VS 2017 is detected and I can install extensions for it?

Install log:

3/15/2017 2:21:53 PM - Microsoft VSIX Installer 3/15/2017 2:21:53 PM - ------------------------------------------- 3/15/2017 2:21:53 PM - Initializing Install... 3/15/2017 2:21:54 PM - Extension Details... 3/15/2017 2:21:54 PM - Identifier : 9289a8ab-1bb6-496b-9992-9f7ea27f66a8 3/15/2017 2:21:54 PM - Name : Roslynator 2017 3/15/2017 2:21:54 PM - Author : Josef Pihrt 3/15/2017 2:21:54 PM - Version : 1.2.51 3/15/2017 2:21:54 PM - Description : A collection of 170+ analyzers and 170+ refactorings for C#, powered by Roslyn. 3/15/2017 2:21:54 PM - Locale : en-US 3/15/2017 2:21:54 PM - MoreInfoURL : http://github.com/JosefPihrt/Roslynator 3/15/2017 2:21:54 PM - InstalledByMSI : False 3/15/2017 2:21:54 PM - SupportedFrameworkVersionRange : [4.6,) 3/15/2017 2:21:54 PM - 3/15/2017 2:21:54 PM - SignatureState : Unsigned 3/15/2017 2:21:54 PM - Supported Products : 3/15/2017 2:21:54 PM - Microsoft.VisualStudio.Community 3/15/2017 2:21:54 PM - Version : [15.0,16.0) 3/15/2017 2:21:54 PM - Microsoft.VisualStudio.Pro 3/15/2017 2:21:54 PM - Version : [15.0,16.0) 3/15/2017 2:21:54 PM - Microsoft.VisualStudio.Enterprise 3/15/2017 2:21:54 PM - Version : [15.0,16.0) 3/15/2017 2:21:54 PM - 3/15/2017 2:21:54 PM - References : 3/15/2017 2:21:54 PM - ------------------------------------------------------- 3/15/2017 2:21:54 PM - Identifier : Microsoft.VisualStudio.MPF.15.0 3/15/2017 2:21:54 PM - Name : Visual Studio MPF 15.0 3/15/2017 2:21:54 PM - Version : [15.0,16.0) 3/15/2017 2:21:54 PM - MoreInfoURL : 3/15/2017 2:21:54 PM - Nested : No 3/15/2017 2:21:54 PM - 3/15/2017 2:21:54 PM - Signature Details... 3/15/2017 2:21:54 PM - Extension is not signed. 3/15/2017 2:21:54 PM - 3/15/2017 2:21:54 PM - Searching for applicable products... 3/15/2017 2:21:54 PM - Found installed product - Microsoft Visual Studio Enterprise 2015 3/15/2017 2:21:54 PM - Found installed product - Microsoft Visual Studio Professional 2015 3/15/2017 2:21:54 PM - Found installed product - Microsoft Visual Studio Community 2015 3/15/2017 2:21:54 PM - Found installed product - Microsoft Visual Studio 2015 Shell (Integrated) 3/15/2017 2:21:54 PM - Found installed product - Global Location 3/15/2017 2:21:54 PM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products. at VSIXInstaller.App.InitializeInstall(Boolean isRepairSupported) at VSIXInstaller.App.InitializeInstall() at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.Execute()
+7
visual-studio visual-studio-2017 visual-studio-extensions
source share
5 answers

From the log file, it looks like the old vsixinstaller.exe, which was trying to install the extension, not VS977. It should be on a path similar to "C: \ Program Files (x86) \ Microsoft Visual Studio \ 2017 \ Enterprise \ Common7 \ IDE \ VSIXInstaller.exe"

Try to explicitly launch it with the Roslynator.VisualStudio.1.2.51.vsix parameter.

+2
source share

As Hans Passant noted, huge changes were made by Microsoft during the installation process, so previous approaches to detecting VS will no longer work. For example, to detect the VS installation folder, now it requires several additional tools or scripts,

https://github.com/Microsoft/vswhere

So for tutorials such as How to Redirect Extension Projects in Visual Studio 2017 , you can follow the tips.

+2
source share

Press Win + R and write the path to the correct version of VSIXIntaller. eg.

"E: \ Microsoft Visual Studio \ 2017 \ Enterprise \ Common7 \ IDE \ VSIXInstaller.exe" "C: \ Users \ jdonoso.IMLG \ Downloads \ Ankh.VS15Package.vsix"

I have 3 versions of Visual Studio, but the correct installer is VS2017, since the package is for VS2017. Keep this in mind.

That is why I had the same error. Solve it using the correct version.

+2
source share

Maybe you should only use the correct installer. One for Visual Studio 2107. Therefore, your path should display C: \ Program Files (x86) \ Microsoft Visual Studio \ 2017 \ Professional \ Common7 \ IDE before any other version of VS.

Professional should be replaced by an established one. Enterprise, Ultimate, ...

+1
source share

Extensions must be recompiled specifically for each version of VS, the associated virtual DLL files are different, so regardless of whether it works in 2015 or not, this is very small.

a) You can try to contact the author (by opening a problem or so), which is probably the best.

b) Or, one thing that may work is trying to recompile the source code , as this may filter out possible versioning options. This has helped me a few times. You need to add “Visual Studio Extension” to your setting in the “Other Tools” section (just restart the installation file and “Change”), and you should be able to create code (although each extension may have some features). Given that the tool is open source, it's probably the route I will take.
As for the reasons why (maybe you are having problems), it’s hard to say that I had some problems with one of the extensions, it could be a mistake (since 2017 is still a bit fresh), it could be somewhat something like problems with versions of the DLL, this may be your setup. So you can also try a new installation or ...

c) trying it on another machine is always useful

-2
source share

More articles:


All Articles