I would like to use the AddProjectDependencyAction but I do not want to gather the project input information from the user through a wizard.  I am able to derive the project names as strings in the recipe but the Action wants EnvDTE.Project types as input.  I attempted to use the ProjectConverter but have been unsuccessful.

Is it possible to convert a string argument into a EnvDTE.Project Argument and then pass that to the AddProjectDependencyAction?

Solution\PostBuild

That's the value you have to use (apparently you didn't try that particular one?).

As I said, the converter takes the virtual path to an item as it appears in the solution explorer, basically concatenating all node names with a path separator. A project looks in the solution explorer with a name, not with the .csproj extension. The easiest way to find out which string to use is to unfold the template once, look at the resulting solution, and do that concatenation manually to build the string.

HTH

<Argument Name="PostBuildProject" Type="EnvDTE.Project, EnvDTE">

<Converter Type="Microsoft.Practices.RecipeFramework.Library.Converters.ProjectConverter, Microsoft.Practices.RecipeFramework.Library"/>

<ValueProvider Type="Evaluator" Expression="\PostBuild" />

</Argument>

<TemplateContent>

<ProjectCollection>

<SolutionFolder Name="Solution">

<SolutionFolder Name="ApplicationArchitecture">

<ProjectTemplateLink ProjectName="$RootNamespace$.DataEntityModel">Projects\CompanyX.GroupX.ProjectX.DataEntityModel\CompanyX.GroupX.ProjectX.DataEntityModel.vstemplate</ProjectTemplateLink>

<ProjectTemplateLink ProjectName="$RootNamespace$.Service.Library">Projects\CompanyX.GroupX.ProjectX.Service.Library\CompanyX.GroupX.ProjectX.Service.Library.vstemplate</ProjectTemplateLink>

<ProjectTemplateLink ProjectName="$RootNamespace$.ServiceAgent">Projects\CompanyX.GroupX.ProjectX.ServiceAgent\CompanyX.GroupX.ProjectX.ServiceAgent.vstemplate</ProjectTemplateLink>

<ProjectTemplateLink ProjectName="$RootNamespace$.Service">Projects\CompanyX.GroupX.ProjectX.Service\CompanyX.GroupX.ProjectX.Service.vstemplate</ProjectTemplateLink>

<ProjectTemplateLink ProjectName="$RootNamespace$.WebApp">Projects\CompanyX.GroupX.ProjectX.WebApp\CompanyX.GroupX.ProjectX.WebApp.vstemplate</ProjectTemplateLink>

</SolutionFolder>

<SolutionFolder Name="TechnicalArchitecture">

<ProjectTemplateLink ProjectName="$CompanyX$.Architecture">Projects\CompanyX.Architecture\CompanyX.Architecture.vstemplate</ProjectTemplateLink>

<ProjectTemplateLink ProjectName="$CompanyX$.Architecture.Test">Projects\CompanyX.Architecture.Test\CompanyX.Architecture.Test.vstemplate</ProjectTemplateLink>

<ProjectTemplateLink ProjectName="$CompanyX$.Architecture.Service.Library">Projects\CompanyX.Architecture.Service.Library\CompanyX.Architecture.Service.Library.vstemplate</ProjectTemplateLink>

<ProjectTemplateLink ProjectName="$CompanyX$.Architecture.Service.Library.Test">Projects\CompanyX.Architecture.Service.Library.Test\CompanyX.Architecture.Service.Library.Test.vstemplate</ProjectTemplateLink>

<ProjectTemplateLink ProjectName="$CompanyX$.Architecture.Service">Projects\CompanyX.Architecture.Service\CompanyX.Architecture.Service.vstemplate</ProjectTemplateLink>

</SolutionFolder>

<ProjectTemplateLink ProjectName="PostBuild">Projects\PostBuild\PostBuild.vstemplate</ProjectTemplateLink>

</SolutionFolder>

</ProjectCollection>

</TemplateContent>

Solution\PostBuild

That's the value you have to use (apparently you didn't try that particular one?).

As I said, the converter takes the virtual path to an item as it appears in the solution explorer, basically concatenating all node names with a path separator. A project looks in the solution explorer with a name, not with the .csproj extension. The easiest way to find out which string to use is to unfold the template once, look at the resulting solution, and do that concatenation manually to build the string.

HTH