This document explains how to include Visual Studio project templates and item templates in your VSIX extension using CodingWithCalvin.VsixSdk.
The built-in VSIX Manifest Designer in Visual Studio cannot enumerate SDK-style projects when adding template assets. This is because the designer uses legacy DTE extenders that are registered for the old project system, not the Common Project System (CPS) used by SDK-style projects.
Additionally, SDK-style projects don't define the TemplateProjectOutputGroup and ItemTemplateOutputGroup MSBuild output groups that VSSDK expects for template assets.
This SDK provides MSBuild-based template support that bypasses these limitations entirely.
The SDK provides four item types for including templates:
| Item Type | Description |
|---|---|
VsixProjectTemplate |
A folder containing a .vstemplate file for a project template |
VsixItemTemplate |
A folder containing a .vstemplate file for an item template |
VsixTemplateZip |
A pre-built template zip file |
VsixTemplateReference |
Reference a template folder from another project |
By default, the SDK automatically discovers templates in your project:
- Project templates: Any subfolder in
ProjectTemplates/containing a.vstemplatefile - Item templates: Any subfolder in
ItemTemplates/containing a.vstemplatefile
MyExtension/
MyExtension.csproj
source.extension.vsixmanifest
ProjectTemplates/
MyProjectTemplate/
MyProjectTemplate.vstemplate
MyProject.csproj
Class1.cs
ItemTemplates/
MyItemTemplate/
MyItemTemplate.vstemplate
MyClass.cs
With this structure, no additional configuration is needed. The SDK will:
- Find the templates automatically
- Zip each template folder during build
- Include the zips in the VSIX at
ProjectTemplates/andItemTemplates/
To disable automatic template discovery:
<PropertyGroup>
<EnableDefaultVsixTemplateItems>false</EnableDefaultVsixTemplateItems>
</PropertyGroup>To use different folder names:
<PropertyGroup>
<VsixProjectTemplatesFolder>Templates\Projects</VsixProjectTemplatesFolder>
<VsixItemTemplatesFolder>Templates\Items</VsixItemTemplatesFolder>
</PropertyGroup>If your templates are in non-standard locations, add them explicitly:
<ItemGroup>
<VsixProjectTemplate Include="MyTemplates\ConsoleApp" />
<VsixItemTemplate Include="MyTemplates\NewClass" />
</ItemGroup>If you have pre-built template zip files:
<ItemGroup>
<VsixTemplateZip Include="Templates\MyTemplate.zip" TemplateType="Project" />
<VsixTemplateZip Include="Templates\MyItem.zip" TemplateType="Item" />
</ItemGroup>To include a template from another project in your solution:
<ItemGroup>
<VsixTemplateReference Include="..\MyTemplateProject\MyTemplateProject.csproj"
TemplateType="Project"
TemplatePath="Templates\MyProjectTemplate" />
</ItemGroup>The TemplatePath is relative to the referenced project's directory.
Visual Studio requires <Content> entries in your .vsixmanifest to register templates. Add these to your manifest:
<Content>
<ProjectTemplate Path="ProjectTemplates" />
<ItemTemplate Path="ItemTemplates" />
</Content>The SDK will emit warnings if you have templates defined but missing manifest entries:
- VSIXSDK011: Project templates defined but no
<ProjectTemplate>in manifest - VSIXSDK012: Item templates defined but no
<ItemTemplate>in manifest
To organize templates into subfolders within the VSIX:
<ItemGroup>
<!-- Will be placed at ProjectTemplates/CSharp/ -->
<VsixProjectTemplate Include="ProjectTemplates\MyTemplate" TargetSubPath="CSharp" />
<!-- Will be placed at ItemTemplates/Web/ -->
<VsixItemTemplate Include="ItemTemplates\MyItem" TargetSubPath="Web" />
</ItemGroup><Project Sdk="CodingWithCalvin.VsixSdk/1.0.0">
<PropertyGroup>
<Version>1.0.0</Version>
</PropertyGroup>
<!-- Templates are auto-discovered, but you can add more explicitly -->
<ItemGroup>
<VsixTemplateReference Include="..\SharedTemplates\SharedTemplates.csproj"
TemplateType="Project"
TemplatePath="Templates\SharedProject" />
</ItemGroup>
</Project><?xml version="1.0" encoding="utf-8"?>
<PackageManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011">
<Metadata>
<Identity Id="MyExtension" Version="1.0.0" Language="en-US" Publisher="MyCompany" />
<DisplayName>My Extension</DisplayName>
<Description>Extension with templates</Description>
</Metadata>
<Installation>
<InstallationTarget Id="Microsoft.VisualStudio.Community" Version="[17.0,19.0)">
<ProductArchitecture>amd64</ProductArchitecture>
</InstallationTarget>
</Installation>
<Content>
<ProjectTemplate Path="ProjectTemplates" />
<ItemTemplate Path="ItemTemplates" />
</Content>
</PackageManifest><?xml version="1.0" encoding="utf-8"?>
<VSTemplate Version="3.0.0" Type="Project" xmlns="http://schemas.microsoft.com/developer/vstemplate/2005">
<TemplateData>
<Name>My Project Template</Name>
<Description>A sample project template</Description>
<Icon>__TemplateIcon.ico</Icon>
<ProjectType>CSharp</ProjectType>
<DefaultName>MyProject</DefaultName>
<ProvideDefaultName>true</ProvideDefaultName>
</TemplateData>
<TemplateContent>
<Project File="MyProject.csproj" ReplaceParameters="true">
<ProjectItem ReplaceParameters="true">Class1.cs</ProjectItem>
</Project>
</TemplateContent>
</VSTemplate>| Code | Description |
|---|---|
| VSIXSDK010 | VsixTemplateZip item missing TemplateType metadata |
| VSIXSDK011 | Project templates defined but no <ProjectTemplate> in manifest |
| VSIXSDK012 | Item templates defined but no <ItemTemplate> in manifest |
| VSIXSDK013 | VsixTemplateReference item missing TemplateType metadata |
| VSIXSDK014 | VsixTemplateReference item missing TemplatePath metadata |
- Ensure your manifest has the appropriate
<Content>entries - Check that the template zip files are included in the VSIX (open the .vsix as a zip)
- Verify the
.vstemplatefile has correct<ProjectType>or<TemplateGroupID> - Reset the Visual Studio template cache: delete
%LocalAppData%\Microsoft\VisualStudio\<version>\ComponentModelCache
Ensure the template folder exists and contains a .vstemplate file. For VsixTemplateReference, verify the TemplatePath is correct relative to the referenced project.
Check the TargetSubPath metadata if you're using custom paths. By default, templates are placed directly in ProjectTemplates/ or ItemTemplates/.