2 Articles match "Static Void","Workflow"

25 Articles match "Static Void","Workflow"

• The Best from DevelopMentor

  MORE

• Flowing transaction into a workflow using WF4
  
  Beta 2 One of the things that wasn’t possible in Windows Workflow Foundation 3 was flowing transaction over a WCF service request into a workflow. Fortunately that is one the problems that Windows Workflow Foundation 4 solves for us. In WF4 we can use the ReceiveAndSendreply template to configure a workflow as a service and accept WCF calls. If we want to use transactions we need to add the TransactedReceiveScope to the workflow. public static string GetReport(). {. static void Main( string [] args). {. else. {. return sb.ToString(); }. }.
  The Problem Solver - Monday, December 21, 2009
  READ MORE
• More Workflow 4 Services and duplex communications
  
  Yesterday I posted a long blog post explaining how to do duplex communications in a Workflow service. Its a long story but the most important points where that workflow services don’t support the same style duplex communication as WCF with the callback channel defined in the ServiceContract but rather something that is called durable duplex where the callback contract is independent and the client has to create a ServiceHost and act as a full-blown WCF service. The code in the Main() function now looks like this: static void Main( string [] args). {. Conclusion.
  The Problem Solver - Tuesday, May 4, 2010
  READ MORE
• Securing a Workflow Service using Windows Identity Foundation
  
  How about securing a workflow service? As a workflow 4 service is just another WCF service securing it is just as easy as the steps below will demonstrate. To start with I created a small workflow service and a simple client application. The console app is real simple and looks like this: static void Main( string [] args). {. The client code now looks like: static void Main( string [] args). {. Tags: NET Workflow WCF WF4 VS2010 WIF No security yet and the client works as expected. try. {. catch (Exception ex). {. Console.ReadLine(); }.
  The Problem Solver - Friday, September 24, 2010
  READ MORE
• Versioning long running Workflow Services in WF4, the code
  
  In my previous WF4 post I described the principal of how to version workflow services using the WCF 4 RoutingService. The workflow service with 2 different versions of same workflow. The second version of the workflow has more activities in the tree so it can’t load workflow instances from version 1. Each workflow is hosted in a different XAMLX file and the second was created by copying the first and making the required changes to it. It knows about one existing workflow instance previously created and will create a new one. class Program. {.
  The Problem Solver - Tuesday, November 16, 2010
  READ MORE
• WF4&WCF and message correlation
  
  This same some more about sending multiple messages to the same workflow, AKA Workflow Correlation. One of the ugly parts of Windows Workflow Foundation 3 was the message correlation part when you used WCF to send multiple messages to the same workflow. This guid was the workflow instance ID but having to use that on the client means the client had to be very aware of the server technology used, something that goes against the principals of WCF. To demonstrate this we first need to expand the workflow so it can receive multiple messages for the same workflow.
  The Problem Solver - Wednesday, September 2, 2009
  READ MORE
• Workflow 4 Services and duplex communications
  
  void Reply( string message); }. static void Main( string [] args). {. public void Reply( string message). {. But with a workflow service this doesn’t work because, without the ServiceContract attribute, there is no way to specify the CallbackContract. Yet workflows support duplex communications. Workflow Services and Durable Duplex. Instead of the normal WCF duplex services workflow services use a mechanism that is called durable duplex. Also settings a workflow, and the client, up for durable duplex takes a bit more configuring.
  The Problem Solver - Monday, May 3, 2010
  READ MORE
• Workflow 4 and soap faults
  
  RC 1 Using the ReceiveAndSendReply activity template and the WorkflowServiceHost it is easy to create a workflow service. Other applications can communicate with the workflow just as if it is a regular WCF service, they never need to know the difference. Throwing a FaultException When a FaultException is thrown in a workflow service pretty much the expected thing is done. But with a workflow service there is no service contract class we can add the attribute to. So how do we specify the fault contract with a workflow service? But what about faults? Enjoy!
  The Problem Solver - Wednesday, March 24, 2010
  READ MORE