locked
different versions of Microsoft.VisualStudio.Shell1.0 RRS feed

  • Question

  • Hello,

    I have the same VSIX Package in two different environments:
    environment 1 is my main machine with VS 2013 and VS2015 RC installed
    environment 2 is a virtual machine with only VS2013 installed.

    When I open my VSIX project in the virtual machine Microsoft.VisualStudio.Shell11.0 is Version 12.0.0.0

    When I open it on my main machine Version is 14.0.0.0

    as Specific Version is set to false, I thought I have no problem with this.

    But when I compile the project and take the VSIX to another PC with only VS 2013 installed,the package is not working.

    In Activitylog is an entry Microsoft.VisualStudio.Shell11.0 Version 14.0.0.0 not found.

    Why does the package expect V14.0.0.0 ?

    Is it related to TargetFramework 4.5.1 ? I have 4.5.2 installed on this machine...



    best regards Stephan Hartmann ML-Software GmbH

    Saturday, May 16, 2015 2:56 AM

Answers

  • I replaced the Shell.11.0 with Shell.12.0 and the problems disappeared.


    best regards Stephan Hartmann ML-Software GmbH

    • Marked as answer by Caillen Monday, May 25, 2015 11:41 AM
    Friday, May 22, 2015 9:36 AM

All replies

  • I also noticed that only 
    Microsoft.VisualStudio.CommandBars and
    Microsoft.VisualStudio.Shell.11.0

    are taken from GAC, all others are taken from SDK folders.

    best regards Stephan Hartmann ML-Software GmbH

    Saturday, May 16, 2015 3:11 AM
  • But when I compile the project and take the VSIX to another PC with only VS 2013 installed,the package is not working.

    Hi,

    Did you build the project in your main machine with VS2015 or the virtual machine with VS2013? Does it work if you install this VSIX package on the virtual machine?

    And please post the original Activitylog error messages as well as the content in the VSIX manifest file.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, May 18, 2015 6:44 AM
  • the workin version was build in virtual pc, the not working version on my main machine (with VS2015) installed.

    Meanwhile we encountered the problem, that the working version did not install in VS2013 (Community Edition) on a pc with VS2013 AND  VS2015 Preview installed.

    Maybe this is related to the Community Edition, because we didn't really tested this before ...

    Here are the requested files:
    the vsix was build on my main machine with VS2013 (and VS2015 installed)
    the log is taken from a seperate PC with only VS2013 installed

    ActivityLog:

      <entry>
        <record>824</record>
        <time>2015/05/18 13:34:42.179</time>
        <type>Information</type>
        <source>VisualStudio</source>
        <description>Begin package load [iNEXTPackage]</description>
        <guid>{E1A0AA20-0FE8-4779-98B0-00E8B8E9D72E}</guid>
      </entry>
      <entry>
        <record>825</record>
        <time>2015/05/18 13:34:42.179</time>
        <type>Error</type>
        <source>VisualStudio</source>
        <description>CreateInstance failed for package [iNEXTPackage]</description>
        <guid>{E1A0AA20-0FE8-4779-98B0-00E8B8E9D72E}</guid>
        <hr>80070002</hr>
        <errorinfo>Die Datei oder Assembly "Microsoft.VisualStudio.Shell.11.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.</errorinfo>
      </entry>
      <entry>
        <record>826</record>
        <time>2015/05/18 13:34:42.179</time>
        <type>Error</type>
        <source>VisualStudio</source>
        <description>End package load [iNEXTPackage]</description>
        <guid>{E1A0AA20-0FE8-4779-98B0-00E8B8E9D72E}</guid>
        <hr>80004005 - E_FAIL</hr>
        <errorinfo>Die Datei oder Assembly "Microsoft.VisualStudio.Shell.11.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.</errorinfo>
      </entry>
    </activity>



    best regards Stephan Hartmann ML-Software GmbH


    • Edited by S. Hartmann Monday, May 18, 2015 1:42 PM added some info
    Monday, May 18, 2015 1:39 PM
  • vsixmanifest

    <PackageManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011">
      <Metadata>
        <Identity Id="e1a0aa20-0fe8-4779-98b0-00e8b8e9d72e" Version="5.0.0.17" Language="en-US" Publisher="ML-Software GmbH" />
        <DisplayName>iNEXT 2015 Visual Studio Extensions </DisplayName>
        <Description xml:space="preserve">iNEXT 2015 VSIX Package for Visual Studio 2013 (TM)</Description>
        <MoreInfo>http://www.inextsuite.com</MoreInfo>
        <License>Licence.txt</License>
        <GettingStartedGuide>GettingStarted.html</GettingStartedGuide>
        <ReleaseNotes>ReleaseNotes.html</ReleaseNotes>
        <Icon>ML_64x64.ico</Icon>
        <Tags>iNEXT 2015, iNEXT Suite</Tags>
      </Metadata>
      <Installation InstalledByMsi="false">
        <InstallationTarget Id="Microsoft.VisualStudio.Pro" Version="[12.0,13.0]" />
      </Installation>
      <Dependencies>
        <Dependency Id="Microsoft.Framework.NDP" DisplayName="Microsoft .NET Framework" Version="4.5" />
        <Dependency Id="Microsoft.VisualStudio.MPF.11.0" DisplayName="Visual Studio MPF 11.0" Version="11.0" />
      </Dependencies>
      <Assets>
        <Asset Type="Microsoft.VisualStudio.VsPackage" Path="iNEXT_VS2013.pkgdef" />
      </Assets>
    </PackageManifest>


    best regards Stephan Hartmann ML-Software GmbH

    Monday, May 18, 2015 1:40 PM
  • For all intents and purposes, the community edition is essentially the same as the professional edition.

    To build a VS extension that targets multiple versions of Visual Studio, you need to build the .VSIX with the earlier version of VS, and then add the newer version(s) to the vsixmanifest.

    Sincerely,


    Ed Dore

    Tuesday, May 19, 2015 12:26 AM
  • Yes, I also think it is not related to the Community Edition.

    But why do I get the wrong reference to Microsoft.VisualStudio.Shell.11.0, Version=14.0.0.0?

    Specific version is set to false, so I would expect VS will use the present Version 12.0.0.0.

    But in Activity log it always complains about missing version 14.0.0.0

    Screenshot is on PC with Visual Studio 2015 RC installed


    best regards Stephan Hartmann ML-Software GmbH


    Friday, May 22, 2015 9:08 AM
  • I replaced the Shell.11.0 with Shell.12.0 and the problems disappeared.


    best regards Stephan Hartmann ML-Software GmbH

    • Marked as answer by Caillen Monday, May 25, 2015 11:41 AM
    Friday, May 22, 2015 9:36 AM