Expose Service recipe error

Topics: General Discussion Forum
Jun 7, 2007 at 1:29 AM
When exposing Services I continue to get Recipe errors. Usually I see this after modifying a namespace. Now I'm seeing this error on newly created DC, SC, and implementation.

I get the Expose Service Dialog no problem, and can select Service implementation class name. I'm choosing Basic WS interop and include MetaData, although any combination of options still lead to an error


Recipe Framework Error
An exception occured during the binding of reference or execution of recipe
ExposeWCFService. Error was: the following arguments are required and don't
have values: ServiceContractNamespace. Can't continue execution..
You can remove the reference to this recipe through the Guidance Package
Manager

details:

Microsoft.Practices.RecipeFramework.RecipeExecutionException: An exception occurred during the binding of reference or execution of recipe ExposeWCFService. Error was: The following arguments are required and don't have values: ServiceContractNamespace. 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()

Jun 7, 2007 at 1:46 AM
Found a solution in post

http://www.codeplex.com/servicefactory/Thread/View.aspx?ThreadId=9218

This makes sense, We normally create company solution file based on our company standards, rather then the vstemplate.

After adding the contract namespace lines the Expose Service recipes now work

GlobalSection(ExtensibilityGlobals) = postSolution
ISWCFSolution = True
Locked = True
UnLocked = False
ServiceContractNamespace = http://XXXXXX.ClientServices.ServiceContracts/2007/06
FaultContractNamespace = http://XXXX.ClientServices.FaultContracts/2007/06
DataContractNamespace = http://XXXXXX.Newport.ClientServices.DataContracts/2007/06
EndGlobalSection