locked
Building and then installing a VSI add-in yields "one or more content items contained within the .vscontent" RRS feed

  • Question

  • I have an existing project, which creates a VSI as the output. The project works nicely for Visual Studio versions 2005, 2008, and 2010.

    I want to add support for Visual Studio 2013.

    I created a new install folder VS2013 and put copies of the .AddIn and .vscontent from 2010 into it.

    According to this page, the ContentVersion number for Visual Studio 2013, should stay the same, namely 2.0. That page has a bug, because the dropdown at the top specifically references 2013, however the text for "Text Value" only goes up to 2012 with a value of 2.0. I changed the version number for Visual Studio in the .AddIn module to 12.0, and then build. I ran into the following error:

    one or more content items contained within the .vscontent cannot be installed because the correct version of the content installer component cannot be found.

    Is there some other file to modify? The source of the two modules are below.

    Thanks in advance,

    Sarah

    .vscontent
    <?xml version="1.0" encoding="utf-8" ?>
    <VSContent xmlns="http://schemas.microsoft.com/developer/vscontent/2005">
      <Content>
        <FileName>BuildVersionIncrement.Addin</FileName>
        <FileName>BuildVersionIncrement.dll</FileName>
        <DisplayName>Build Version Increment Addin</DisplayName>
        <Description>Auto increments the build number of all projects of current solution.</Description>
        <FileContentType>Addin</FileContentType>
        <ContentVersion>2.0</ContentVersion>
      </Content>
    </VSContent>
    
    .AddIn
    <?xml version="1.0" encoding="UTF-16" standalone="no"?>
    <Extensibility xmlns="http://schemas.microsoft.com/AutomationExtensibility">
    	<HostApplication>
    		<Name>Microsoft Visual Studio</Name>
    		<Version>12.0</Version>
    	</HostApplication>
    	<Addin>
    		<FriendlyName>BuildVersionIncrement</FriendlyName>
    		<Description>Auto increments the build version of .net projects.</Description>
    		<Assembly>BuildVersionIncrement.dll</Assembly>
    		<FullClassName>BuildVersionIncrement.Connect</FullClassName>
    		<LoadBehavior>5</LoadBehavior>
    		<CommandPreload>1</CommandPreload>
    		<CommandLineSafe>1</CommandLineSafe>
    	</Addin>
    </Extensibility>


    Tuesday, October 29, 2013 8:02 PM

Answers

  • While it's true add-ins are now considered deprecated. They can still be created and used in VS 2013 (I suspect the inclusion of the addin project template was an oversight for VS 2013), and the documentation link Jane mentioned is clearly in error. But going forward beyond VS 2013, extending the IDE should be done with custom VS Packages.

    That being said, I don't believe anything was done to preclude deployment of add-ins via .VSI files for VS 2013.  Any chance you could share out that .VSI file, so we could have a look?

    Sincerely,


    Ed Dore

    Thursday, October 31, 2013 5:31 AM

All replies

  • Hi Sarah,

    Like this thread, I am moving your thread into the Visual Studio Extensibility Forum for dedicated support. Thanks for your understanding.

    Best Regards,


    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.

    Wednesday, October 30, 2013 7:47 AM
  • Hi Sarah,

    Visual Studio add-ins are deprecated in Visual Studio 2013. You can still use existing add-ins, but you can't create new ones. We recommend that you convert add-ins to VSPackages if you want to modify or distribute them.

    For more details, please refer to How to: Convert an Add-in to a VSPackage .

    Best Regards,

    Jane.


    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.

    Wednesday, October 30, 2013 8:26 AM
  • While it's true add-ins are now considered deprecated. They can still be created and used in VS 2013 (I suspect the inclusion of the addin project template was an oversight for VS 2013), and the documentation link Jane mentioned is clearly in error. But going forward beyond VS 2013, extending the IDE should be done with custom VS Packages.

    That being said, I don't believe anything was done to preclude deployment of add-ins via .VSI files for VS 2013.  Any chance you could share out that .VSI file, so we could have a look?

    Sincerely,


    Ed Dore

    Thursday, October 31, 2013 5:31 AM
  • Thank you for your rectification, Ed.

    Sincerely,

    Jane.


    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.

    Thursday, October 31, 2013 9:17 AM