Content Element (VSX Schema)
Contains references to the installable components of the VSIX package.
<Content>
<Assembly>...</Assembly>
<CustomExtension>...</CustomExtension>
<ItemTemplate>...</ItemTemplate>
<MEFComponent>...<MEFComponent>
<ProjectTemplate>...</ProjectTemplate>
<ToolboxControl>...</ToolboxControl>
<VSPackage>...</VSPackage>
</Content>
Attributes and Elements
The following sections describe attributes, child elements, and parent elements.
Attributes
Attribute |
Description |
---|---|
None |
Child Elements
Element |
Description |
---|---|
Optional. Specifies an assembly to install. |
|
Optional. Specifies a custom extension to install and specifies its type. |
|
Optional. Specifies an item template to install. |
|
Optional. Specifies a MEF component to install. |
|
Optional. Specifies a project template to install. |
|
Optional. Specifies a Toolbox control to install. |
|
Optional. Specifies a VSPackage to install. |
Parent Elements
Element |
Description |
---|---|
Required. Provides the root element for a manifest that describes an extension deployment package. |
Remarks
All extension components should have references in the Content element except for components that are included only as dependencies. Dependencies are referenced from the References Element. Dependencies are contained in their own nested VSIX packages and installed immediately before the dependent extension, as required.
Technically, the Content element is optional. However, a VSIX package that does not have a Content element, or has an empty Content element, will not install anything except dependencies.
Element Information
Namespace |
https://schemas.microsoft.com/developer/vsx-schema/2010 |
Schema Name |
VSIX Manifest |
Validation File |
VSIXManifestSchema.xsd |
Can be Empty |
Yes |