I installed the Feb '07 GAX and GAT and create a new guidance project. I build the project with no modifications. During the build I get the error:
Error1'PostBuildEvent' failed with error code '1' 'Unspecified error'C:\Documents and Settings\Keith\My Documents\Visual Studio 2005\Projects\GuidancePackage8\GuidancePackage8Setup\GuidancePackage8Setup.vdprojGuidancePackage8Setup
Then when I try to register the package I get the following error:
Microsoft.Practices.RecipeFramework.ActionExecutionException: An exception occurred during the binding of reference or execution of recipe Register. Error was: Action Register failed to execute: Object reference not set to an instance of an object.. You can remove the reference to this recipe through the Guidance Package Manager. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Practices.RecipeFramework.MetaGuidancePackage.Registration.PackageRegistationAction.GetCommandProcessorAutoRunValue(String& localMachineValue, String& currentUserValue) at Microsoft.Practices.RecipeFramework.MetaGuidancePackage.Registration.PackageRegistationAction.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.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 have "repaired" visual studio 2005, have sp1 installed, and have uninstalled and reinstalled GAX and GAT several times - to no avail. Any ideas? |
| kstrain Saturday, April 21, 2007 1:22 AM |
Hi, The only thing that could cause that exception is that you don't have one of the following registry entries,
Local Machine\Software\Microsoft\Command Processor\AutoRun Current User\Software\Microsoft\Command Processor\AutoRun
If you don't have any of those entries, you can avoid the exception, creating the entries. what OS are you running?
|
| Jose Escrich Wednesday, April 25, 2007 6:36 PM |
Jose Escrich,
Thank you for your assistance. Command Processor was not a key defined on my computer under HKEY_CURRENT_USER/Software/Microsoft, but I had it under HKEY_LOCAL_MACHINE, so I copied the key over to HKEY_CURRENT_USER and it worked nicely. By the way, I am running Windows XP SP2 on a Pentium Core Duo extreme. |
| kstrain Sunday, April 29, 2007 3:26 AM |
Hi Lukasz,
This one is new to us. So you're saying that if installutil can't write to the log file (because it's read only due to be checked into source control) it will then fail? Not sure if there is much we can do from the GAX side here besides not specifying a logfile or somehow tell installutil not to fail if log can't be written to.
btw, do you really need to check in the log file into source control? (at first, this looks more like a per-machine per-developer info to me and not something to share with others).
thanks, -Victor.
|
| vga Monday, April 30, 2007 3:30 AM |
Additional Note:
If I close visual studio and run the setup msi for the package,it works properly. It just won't register in visual studio.
|
| kstrain Saturday, April 21, 2007 1:39 AM |
Hi, The only thing that could cause that exception is that you don't have one of the following registry entries,
Local Machine\Software\Microsoft\Command Processor\AutoRun Current User\Software\Microsoft\Command Processor\AutoRun
If you don't have any of those entries, you can avoid the exception, creating the entries. what OS are you running?
|
| Jose Escrich Wednesday, April 25, 2007 6:36 PM |
I am experiencing the same problem. But it occurs when trying to register to the experimental hive ( so I can interact with DSL's). I've added the entries mentioned to no avail. I'm running on XP SP2.
Regards Darren Bell
|
| DarrenARBell Friday, April 27, 2007 8:26 AM |
Hi
I have noticed similar problem while I register guidance package using VS. This problem occurs because I was using source control and I haven't check out InstallUtil.InstallLog file. You can have another cause of thisproblem but it is very useful to change the output from Microsoft Recipe Framework.
Hope this help.
regards,
Lukasz |
| faf38 Saturday, April 28, 2007 7:11 PM |
Jose Escrich,
Thank you for your assistance. Command Processor was not a key defined on my computer under HKEY_CURRENT_USER/Software/Microsoft, but I had it under HKEY_LOCAL_MACHINE, so I copied the key over to HKEY_CURRENT_USER and it worked nicely. By the way, I am running Windows XP SP2 on a Pentium Core Duo extreme. |
| kstrain Sunday, April 29, 2007 3:26 AM |
Hi Lukasz,
This one is new to us. So you're saying that if installutil can't write to the log file (because it's read only due to be checked into source control) it will then fail? Not sure if there is much we can do from the GAX side here besides not specifying a logfile or somehow tell installutil not to fail if log can't be written to.
btw, do you really need to check in the log file into source control? (at first, this looks more like a per-machine per-developer info to me and not something to share with others).
thanks, -Victor.
|
| vga Monday, April 30, 2007 3:30 AM |
Hi Victor,
Yes indeed,if instalutil can't write to log registration of a Guidance Package will fail. I suppose there is not much to do from your side but this issue can occurs on someone else machine (e.g. if someone will add this file tosource control anddo not check out,or installutil have no permissions to write to log file).
What about your second question you have absolutely right. There is no need to add the log file to source control. I have added it by accident (I have just added all solution). Big thanks for your explanations .
Regards,
Łukasz |
| faf38 Monday, April 30, 2007 9:59 AM |
I'm having the same issue after trying to register a package with the Feb 07 release.
I have entries for both Current_User and Local_Machine but they have different values.
Current_User:
Name: Default Value: Not Set
Name: AutoRun Value: Empty
Name: CompletionChar Value: 9
Name: DefaultColor Value: 0
Name: EnableExtensions Value: 1
Local_Machine:
Name: Default Value: Not Set
Name: AutoRun Value: Empty
Name: CompletionChar Value: 40
Name: DefaultColor Value: 0
Name: EnableExtensions Value: 1
Name: PathCompletionChar Value: 40
Here's the output error:
Microsoft.Practices.RecipeFramework.ActionExecutionException: An exception occurred during the binding of reference or execution of recipe Register. Error was: Action Register failed to execute: Failed to process package. See the Guidance Package Development output window for more information about the error.. You can remove the reference to this recipe through the Guidance Package Manager. ---> System.Configuration.Install.InstallException: Failed to process package. See the Guidance Package Development output window for more information about the error. at Microsoft.Practices.RecipeFramework.MetaGuidancePackage.Registration.PackageRegistationAction.ThrowFailure(DTE vs, String currentOperation, String output) at Microsoft.Practices.RecipeFramework.MetaGuidancePackage.Registration.PackageRegistationAction.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.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()
Any ideas?
-Kosmo
|
| Kosmo007 Friday, May 11, 2007 12:50 PM |
Hi Could you please show output from Microsoft recipe Framework? Maybe there I can find more information I be able to help you. Regards Łukasz
|
| faf38 Friday, May 11, 2007 12:59 PM |
Lukasz,
Thanks for your response. I decided to start from scratch and recreate everything. I am able to get it to register now so it was likely an issue with either my xml file or one of the vstemplate files.
Thanks,
Kosmo |
| Kosmo007 Friday, May 11, 2007 3:16 PM |
No problem Kosmo, That's good that you manage to go forward. Very often problems with registering guidance package occurs when you have opened project which is using your guidance package, or installer have no access to some files. The best place to investigate what is wrong is the Microsoft recipe Framework. If this don't solve your problem sometimes restarting system help  Regards, Lukasz |
| faf38 Friday, May 11, 2007 3:23 PM |
Hi ,
I hade the same problem and created from scratch and got registratio recipe to work. I relize that the first time I hade the other solution open in the VS and not saved when I created the GP but next time I created GP from new instance of VS.
Strange ,a bug in the VS ???
Ludwik |
| Ludwik Thursday, August 23, 2007 10:28 AM |