Hi All,

I am trying to load the July 07 smart client guidance in VS2008 but get a "Recipe framework Error" when I go into the Guidance Package Manager and try and enable the package. I have installed the latest GAT and GAX.

Thanks in advance

Microsoft.Practices.RecipeFramework.ActionExecutionException: An exception occurred during the binding of reference or execution of recipe BindingRecipe. Error was: Action FoundationalModuleRefVB failed to execute:
Cannot find registration information for template "C:\Program Files\Microsoft Smart Client Factory\Guidance Package\Templates\Projects\Module.VB\ModuleHandle.vstemplate". Package templates may not be properly registered. Run package installation again and verify template name and location..
You can remove the reference to this recipe through the Guidance Package Manager. ---> System.InvalidOperationException: Cannot find registration information for template "C:\Program Files\Microsoft Smart Client Factory\Guidance Package\Templates\Projects\Module.VB\ModuleHandle.vstemplate". Package templates may not be properly registered. Run package installation again and verify template name and location.
at Microsoft.Practices.RecipeFramework.VisualStudio.Templates.VSTemplatesService.GetTemplateRegistryData(String templateFileName)
at Microsoft.Practices.RecipeFramework.VisualStudio.Templates.VSTemplatesService.Microsoft.Practices.RecipeFramework.VisualStudio.Common.IVsTemplatesService.GetTemplate(String templateFileName)
at Microsoft.Practices.RecipeFramework.VisualStudio.Templates.TemplateReference.OnSited()
at Microsoft.Practices.RecipeFramework.AssetReference.set_Site(ISite value)
at System.ComponentModel.Container.Add(IComponent component, String name)
at Microsoft.Practices.RecipeFramework.Services.AssetReferenceService.Add(IComponent component, String name)
at System.ComponentModel.Container.Add(IComponent component)
at Microsoft.Practices.RecipeFramework.Services.AssetReferenceService.Add(IAssetReference reference, IDictionary initialState, Boolean throwIfDuplicate)
at Microsoft.Practices.RecipeFramework.Services.AssetReferenceService.Add(IAssetReference reference, IDictionary initialState)
at Microsoft.Practices.RecipeFramework.Services.AssetReferenceService.Add(IAssetReference reference)
at Microsoft.Practices.RecipeFramework.Library.Actions.CreateUnboundReferenceAction.Execute()
at Microsoft.Practices.RecipeFramework.Recipe.Microsoft.Practices.RecipeFramework.Services.IActionExecutionService.Execute(String actionName, Dictionary`2 inputValues)
at Microsoft.Practices.RecipeFramework.Recipe.Microsoft.Practices.RecipeFramework.Services.IActionExecutionService.Execute(String actionName)
at Microsoft.Practices.RecipeFramework.Recipe.Microsoft.Practices.RecipeFramework.Services.IActionCoordinationService.Run(Dictionary`2 declaredActions, XmlElement coordinationData)
at Microsoft.Practices.RecipeFramework.Recipe.ExecuteActions(IDictionaryService readOnlyArguments, IDictionaryService arguments, ITypeResolutionService resolution)
--- End of inner exception stack trace ---
at Microsoft.Practices.RecipeFramework.Recipe.UndoExecutedActionsAndRethrow(Exception ex)
at Microsoft.Practices.RecipeFramework.Recipe.ExecuteActions(IDictionaryService readOnlyArguments, IDictionaryService arguments, ITypeResolutionService resolution)
at Microsoft.Practices.RecipeFramework.Recipe.Execute(Boolean allowSuspend)
at Microsoft.Practices.RecipeFramework.GuidancePackage.Execute(String recipe, IAssetReference reference, IDictionary arguments)
at Microsoft.Practices.RecipeFramework.RecipeManager.Add(IComponent component, String name)
at System.ComponentModel.Container.Add(IComponent component)
at Microsoft.Practices.RecipeFramework.RecipeManager.EnablePackage(XmlReader configuration)
at Microsoft.Practices.RecipeFramework.RecipeManager.EnablePackage(String packageName)
at Microsoft.Practices.RecipeFramework.PackageManagement.EnableDisablePackages.OnOkClick(Object sender, EventArgs e)

This is in reply to the VB.NET SCSFproblem.

Does it make sense to install VB.NET? Yes, you are far more productiv, at least in your case.

I have the exact same problem. At VS2008installation time I opted for c# and deselected the VB.NET language. This is probably the reason, and it is a good one having a look at the stack trace.

Find some more info here, go to the end:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2232476&SiteID=1

I will just add VB.NET in VS and do the repare in SCSF, hope it does the job.

Should I let you know?

Peter

The specs in case it matters.

XP SP2

VS2005 is installed

VS2008 is RTM

There were no betas installed on this machine so no uninstall issues should be there.

Thanks

This is in reply to the VB.NET SCSFproblem.

Does it make sense to install VB.NET? Yes, you are far more productiv, at least in your case.

I have the exact same problem. At VS2008installation time I opted for c# and deselected the VB.NET language. This is probably the reason, and it is a good one having a look at the stack trace.

Find some more info here, go to the end:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2232476&SiteID=1

I will just add VB.NET in VS and do the repare in SCSF, hope it does the job.

Should I let you know?

Peter

Adding Vb made it work. Thanks for the help

Mike