Hi Trevor, The workflow Send Activity should only require information from the app.config if the client proxy is not created and fully specified in code. Maybe the endpoint proxy needs to be created when the workflow itself is created. It is possible to build client configuration & endpoint in code eg. Programming WCF Services - ORielly p43-44 Call me offline Trev if you need more info. Cheers Michael
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Richard Sent: Thursday, 19 June 2008 12:00 PM To: listserver@ozMOSS.com Subject: RE: [OzMOSS] RE: Invoking WCF Web Service call from SharePoint Workflow Hi Trevor, I can't directly answer your question but yesterday I was reading this blog post by Sahil about SharePoint and WCF. It might put you on the right path: http://blah.winsmarts.com/2008-5-SharePoint_as_a_WCF_Host.aspx Ed Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Trevor Andrew Sent: Thursday, 19 June 2008 11:20 AM To: listserver@ozMOSS.com Subject: [OzMOSS] RE: Invoking WCF Web Service call from SharePoint Workflow Hi All, We are writing a SharePoint State Machine Workflow, and are trying to use the .NET 3.5 Send Activity to invoke a WCF workflow. The hurdle we are hitting is that when deployed to SharePoint, the Workflow Send Activity still appears to need an app.config file with all of the WCF client configuration / endpoints etc ... Where would such a config file need to be deployed to? What would it be named? How would we ensure our workflow, when running in the context of SharePoint can unambiguously find this config file? Or do we need to augment some current SharePoint config file? The workflow assembly is deployed to the GAC, and the various feature.xml / workflow.xml configuration files are currently being deployed straight out of VS 2008, with a view to feature based deployment into UAT / production ... Any suggestions or hard-won experience from the trenches would be much appreciated. Cheers, Trevor Andrew ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
