Create a project or item template from your existing project and share the VSIX file directly or on the Visual Studio Gallery. You can add a wizard to your template and pick the framework version your template will target.
It's good for packaging basic templates into a VSIX package, but is does not provide support for many advanced template options. For example, you can only package a single Item Template into the VSIX package, so this tool is not an option if you want to deploy many Item Templates in a single VSIX package. Also, it does not allow you to define a custom Category for your Item Templates to appear under in the "Add new file" dialog. There is also a bug where the wizard cannot see files that are within a folder; if you want to create an Item Template from a file, the file must be directly in the project (cannot be contained in a folder within the project). So for creating some basic templates this tool is alright, but if you are serious about item templates you will likely want to create them the old fashion way. If this extension was actively updated I'm sure it could be totally awesome though (hasn't been updated in a year and a half).
It's good as it allows the simple export of multi project solutions to a visual studio project template. But it lacks some details, you would need for seriously developing project templates. For example it does not include the pdb files of wizard dll's. Thus you cannot debug a template wizard. Other thing is that the first project in a multi solution template determines the type of project for the template. You cannot change it later. It supports solution folders, but it is a good idea to locate each project in the same solution folder to a dedicated physical folder. Otherwise the project won't build when created from the template.
1.) The project type of the multi project template is currently implicitly determined by the first project that was added to a solution. e.g. If your first project in a multi project soltuion you want to export as template is a modeling project your template will be always be a modeling template. You cannot change or modify the project type of the template.
In my eyes this is more like a bug in the current version.
2.) Include pdb files of the wizard.dll if available. In order to debug my wizard I currently have to add the pdb file manually to the vsix container.
3.) You should be able to set the startup project in a solution template.
I am trying to create a Windows Azure Cloud service template.
I have a Cloud service project(Extension .ccproj) and a WebRole project with extension .csproj. But when I include both while creating VSIX I am getting the following error : 'startIndex can not be larger than length of string'.
Is windows azure cloud service not supported for this.
Brij Mohan Pandey
I get the same error 'startIndex can not be larger than length of string'. My project is a C makefile proj. with folders added with read-only sources. I would like to make a proj referencing the same files and not copy them :(.
I'm trying to create a template to a standard DLL project and I got the same error 'startIndex can not be larger than length of string. Parameter name: startIndex` does anyone find a solution for that ?
When I try to "Export template as VSIX..." a VC++ project I get the following error:
"startIndex cannot be larger than length of string
Parameter name: startIndex"
Does it work for VC++ projects at all?
I successfully used this extension but I hava just one (very important) issue.
Setting $safeprojectname$ instead of namespace name works correctly (it's correctly replaced) but I need to set this variable also for build->output path. If i do it variable is not replaced with project name. How can I solve it? I need to make also output dir dynamic, it should be created basing on project name. Can you help me?
I was able to get this to work in VS 2012 *sorta*. I extracted the VSIX contents, modified the manifest to allow it to install in VS 2012, it works, but the wizard has certain things that are hard coded to VS 2010, e.g. the editions and the target frameworks. I can just let it generate the templates, then hand modify the manifest files but I would prefer a version that is targeting VS 2012.
It would be awesome if this was either updated or open sourced, I would be willing to make the changes but I am missing the source code for these items:
Even without a new version, this is hands down better than the default "Export to Template" functionality in VS since it allows me to export more than one project at a time. Great extension :)