locked
Command Line VSIX installer issue RRS feed

  • Question

  • Hi All,

    I am using VSIX installer for installing my custom VSIX into Visual Studio 2017. I have used Command line process to install VSIX.

    Command line Installation:

    VSIXInstaller.exe "VSIXFilePath" \q

    Some of times extension was disabled by default in Visual Studio. I have uninstalled it and installed VSIX manually. It enbled in Visual Studio properly. Again uninstalled it and tried to install via command prompt as above, VSIX disabled by default in Visual Studio.

    Can anyone suggest me what could be the reason for this and how to resolve this?

    Regards,
    Cheran
    • Moved by 宝宝徐 Tuesday, January 24, 2017 7:40 AM
    Monday, January 23, 2017 5:35 AM

All replies

  • Hi,

    In previous versions of VS (such as VS 2015) an extension got disabled on every restart after an update if somehow the previous installation was not removed, that is, if two folders (with random names) inside the following folder contained the same extension:

    C:\Users\<user>AppData\Local\Microsoft\VisualStudio\14.0\Extensions

    The workaround was to delete the two folders and install again.

    That said, the VSIX installer of VS 2017 RC is new and uses a different approach, forcing you to close all VS instances and related processes, batching installations, etc. As such, it can have bugs (I reported one that is pending to be released).

    I suggest you to open a bug report ASAP on Microsoft Connect (https://connect.microsoft.com/VisualStudio) with a repro scenario for Microsoft to verify and fix.

    PS: Notice that the correct syntax is /q not \q


    My portal and blog about VSX: http://www.visualstudioextensibility.com<br/> Twitter: https://twitter.com/VSExtensibility<br/> MZ-Tools productivity extension for Visual Studio: https://www.mztools.com

    Monday, January 23, 2017 11:02 AM
  • Hi Cheran,

    Thank you for posting in MSDN forum.

    This forum is about Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor.

    As your issue is related to VSIX, I help you move this case to VSIX forum for dedicated support.

    Thank you for your understanding,

    Best Regards,


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, January 24, 2017 7:39 AM