Developing a Guidance package.
I have a solution template which includes this TemplateData element:
<?xml version="1.0" encoding="Windows-1252"?>
<VSTemplate
Version="2.0"
Type="ProjectGroup"
xmlns="http://schemas.microsoft.com/developer/vstemplate/2005">
<TemplateData>
<Name>Módulos Presentación</Name>
<Description>Solución para la creación de uno o más módulos PULSAR 3 de capa Presentación</Description>
<ProjectType>CSharp</ProjectType>
<SortOrder>90</SortOrder>
<Icon>Evolutio.ico</Icon>
<CreateNewFolder>false</CreateNewFolder>
<DefaultName>Pulsar.Cliente.Mods</DefaultName>
<ProvideDefaultName>true</ProvideDefaultName>
</TemplateData>
<TemplateContent>
<ProjectCollection>
<SolutionFolder Name="gral" />
<SolutionFolder Name="spec">
<SolutionFolder Name="mock" />
<SolutionFolder Name="specs" />
<SolutionFolder Name="tests" />
</SolutionFolder>
<SolutionFolder Name="src">
<SolutionFolder Name="ui">
<SolutionFolder Name="mod">
<ProjectTemplateLink ProjectName="$ProjectName$">Projects\Mod\Mod.vstemplate</ProjectTemplateLink>
</SolutionFolder>
</SolutionFolder>
</SolutionFolder>
</ProjectCollection>
</TemplateContent>
<WizardExtension>
<Assembly>Microsoft.Practices.RecipeFramework.VisualStudio, Version=1.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a</Assembly>
<FullClassName>Microsoft.Practices.RecipeFramework.VisualStudio.Templates.UnfoldTemplate</FullClassName>
</WizardExtension>
<WizardData>
<Template xmlns="http://schemas.microsoft.com/pag/gax-template"
SchemaVersion="1.0"
Recipe="CrearSlnModsUi">
<References>
</References>
</Template>
</WizardData>
</VSTemplate>
(for those who can't see the picture, it shows the name as something similar to "Módulos Presentación", instead of "Módulos Presentación", and the description text is mangled as well).
I obviously know this is a problem with unicode de/encoding somewhere in the pipe, but have tried saving the xml/vstemplate files in UTF8, UTF16, UTF16 bigendian, charset 1251, and using the ¢ entity, unregistering and registering the package each time, with no luck whatsoever.
What's the work-around? Is there any switch for specifying the package treatment of unicode strings?
Can one use the <Name Package="{guid}" ID="id" /> format for GAX packages? where should then I define the resources?