[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 attachment: winmail.dat
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] Automatic SP1 Patch?
Hello, I am looking at a MOSS 2007 farm which was setup over a year ago and has not had Service Pack 1 installed yet. BUT - when attempting to restore a site collection backup of a site in the farm to a pre-SP1 development VPC it wouldn't restore and reported that it was of a newer version. So I restored to a SP1 development environment and it worked. So we double checked the version number for the farm and it's - 12.0.0.6039 and not 12.0.0.4518 This suggests the Farm has had SP1 applied, but it was not applied by anyone! So my question can a MOSS 2007 farm environment automatically patch itself to SP1 with a Windows update or KB. Is this possible? I am concerned if there are any manual steps that must be taken as well that have been missed? Has anyone else experienced this? Regards, Sezai Kömür Senior Developer - BEng, BSc [cid:image001.gif@01C8D1EF.F6AF9470] Vivid Group Sydney Level 57, MLC Centre Martin Place Sydney, NSW, 2000 Melbourne Level 40 140 William Street Melbourne, Vic, 3000 Perth 200 Wellington Street Perth, WA, 6000 FREECALL: 1800 632 341 FREEFAX: 1800 010 888 www.vividgroup.com.auhttp://www.vividgroup.com.au/ www.moss2007.com.auhttp://www.moss2007.com.au/ Disclaimer: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you have received this email in error, please notify us immediately by return email or telephone 1800 632 341 and destroy the original message. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. Thank you. --- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com inline: image001.gif
RE: [OzMOSS] RE: Invoking WCF Web Service call from SharePoint Workflow
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
