1
Vote

Better Exception Messages

description

Hi Guys,
 
I'm developing a set of Visual Studio packages and I really like using this tool, right up until the point where it breaks for no apparent reason. If you create a VS Package using the menu option provided, the tools work. I don't use all of the tools provided and I use a fair bit of custom code/processes. As package development progresses, my packages usually get to a stage where VS SDK Assist no longer works and it dies with exception messages which are hard to decipher.
 
The reason for my post today is because 'Create > VS Tool Window' has just broken. It was fine this morning, but now it just won't execute. The wizard shows up and I fill in all the options and then it dies with the exception:
 
Microsoft.Practices.RecipeFramework.RecipeExecutionException: An exception occurred during the binding of reference or execution of recipe CreateVSToolWindow. Error was: The following arguments are required and don't have values: VSPackageCodeClass. Can't continue execution..
You can remove the reference to this recipe through the Guidance Package Manager.
at Microsoft.Practices.RecipeFramework.Recipe.ThrowIfRequiredArgumentsAreNull(IDictionaryService arguments)
at Microsoft.Practices.RecipeFramework.Recipe.Execute(Boolean allowSuspend)
at Microsoft.Practices.RecipeFramework.GuidancePackage.Execute(String recipe, IAssetReference reference, IDictionary arguments)
at Microsoft.Practices.RecipeFramework.GuidancePackage.Execute(IAssetReference reference)
at Microsoft.Practices.RecipeFramework.RecipeReference.OnExecute()
at Microsoft.Practices.RecipeFramework.AssetReference.Execute()
at Microsoft.Practices.RecipeFramework.VisualStudio.RecipeMenuCommand.OnExec()
at Microsoft.Practices.RecipeFramework.VisualStudio.AssetMenuCommand.Invoke()
 
I've filled in valid values, but the command just won't execute for the current solution. In the exception messages, it would be nice if there were some resolution steps or a exception dialog like the one that SQL server provides (maybe use that?). I'm happy to change my solution so that it fits within the bounds of a VS SDK Assist supported configuration, though I'm not really sure what that is. Some configurations break VS SDK assist. It would be nice to find out what is supported and what is not.
 
Cheers,
 
 
Matt

comments