I finally checked the solution described here .
The idea is that we need to add an assembly that implements IWizard in the GAC, or to any other place that Visual Studio looks for using the assembly assembly mechanism. VS is looking for our template assembly next to it (devenv.exe) in C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE
. It also appears in two subdirectories: PrivateAssemblies
and PublicAssemblies
.
I'm not sure whether to sign our assembly with a strong key or not (I use signed in my case). You can easily check it out.
So, if I am not mistaken, it is impossible to force the assembly to be used directly from your zip template file . To simplify the use and updating of my template, I am going to create a small installation project.
Last note. As far as I know, you should not specify the .dll extension of your assembly in the Assembly tag. This is how I write the vstemplate part for my build extension wizard:
<WizardExtension> <Assembly>WpfTaskTemplateWizard, Version=1.0.0.0, Culture=Neutral, PublicKeyToken=22050f445905b871</Assembly> <FullClassName>WpfTaskTemplateWizard.UIWizard</FullClassName> </WizardExtension>
source share