Wish I could take all the credit! Thanks are mainly due to Rob Slaney who I bounced the idea off. (And yes, Juval of course) Cheers Michael
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Trevor Andrew Sent: Friday, 20 June 2008 5:25 PM To: listserver@ozMOSS.com Subject: RE: [OzMOSS] RE: Invoking WCF Web Service call from SharePoint Workflow Hi All, Just a quick note to let the list know that I got this going using Michael's suggestion of using a programmatically created WCF service proxy client, which needs no "config" file anywhere. I'd actually attempted that before, but it had failed with a very cryptic error regarding "content /multi-part", which has subsequently seemed to be related to the parameters I set on the binding object. The example code from Juval Lowy's book is very brief, uses no custom parameters on the binding object, and get's it all going from within the SharePoint Workflow ... Binding wsBinding = new WSHttpBinding( ); EndpointAddress endpointAddress = new EndpointAddress("http://localhost:8000/MyService/";); MyContractClient proxy = new MyContractClient(wsBinding,endpointAddress); proxy.MyMethod( ); proxy.Close( ); So Thank you to Michael and Juval ... Cheers, Trevor From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Trevor Andrew Sent: Thursday, 19 June 2008 3:59 PM To: listserver@ozMOSS.com Subject: RE: [OzMOSS] RE: Invoking WCF Web Service call from SharePoint Workflow Hi Aaron, No luck unfortunately. I found the following post where the guy was wanting to do pretty much exactly what I was wanting to do. He appeared to get it going, but I'm having no luck. http://suguk.org/forums/thread/9421.aspx I've tried adding the WCF configuration stuff to the web.config (@ c:\inetput\wss\virtualdirectories\80), I've even tried adding the WCF configuration info into the machine.config, but all to no avail. The message I constantly get is: Could not find endpoint element with name 'WSHttpBinding_IAIPS' and contract 'AIPSWCF.IAIPS' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this name could be found in the client element. The configuration information is identical to that used in another ASP.NET harness web application for exercising the WCF service ... so I'm a bit stuck. I've also been running FileMon while the workflow is running, and it seems the only .config file accessed by the OWSTIMER service is the machine.config. Once again, any suggestions welcome! Cheers, Trevor From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Saikovski Sent: Thursday, 19 June 2008 11:41 AM To: listserver@ozMOSS.com Subject: RE: [OzMOSS] RE: Invoking WCF Web Service call from SharePoint Workflow Hi Trevor, Couldn't you add the WCF settings to the web.config of the site that is making the call? Haven't tried this myself but that's where I would start. You should be able to use the Visual studio WCF config editor to edit the file for you. See how you go. Cheers, Aaron 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 ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
