Microsoft "Dublin"

[kevchadders]

You may all be interested in this!

Dublin is about joining WF to WCF seamlessly

.NET 4.0 will contain major improvements in both WF and WCF. The two will be integrated seamlessly together from the programming model to the runtime. Workflows and services are tightly coupled and both can be declaratively modeled by XAML. With the significant performance improvements in the runtime, the new workflow framework will enable a broad spectrum of model-driven programming scenarios.

Microsoft is enhancing Windows Server’s application server role with a set of extensions codenamed “Dublin”. “Dublin” extends Internet Information Services (IIS) and provides an easy-to-manage platform for developing, deploying and reliably hosting middle-tier WCF/WF services. “Dublin” will simplify the deployment, configuration, management, and scalability of composite applications, while allowing developers to use their existing skills with Visual Studio, the .NET Framework and IIS.

This new Windows Server application server capability will be delivered as a separate release of technologies that can be downloaded and used by Windows Server customers.

Links

http://social.msdn.microsoft.com/For...ublin/threads/

http://connect.microsoft.com/dublin

http://blogs.msdn.com/brunoterkaly/a...ancements.aspx

[chris128]

Cool, I had heard about this Dublin thing a while ago but hadnt seen much of it recently and to be honest I didnt completely understand what its purpose was so I'll be sure to check out those links thanks

[mendhak]

I was just creating a presentation on it

You can do WCF declaratively (from devx)-

<ServiceContract Name="IHelloWorld">
 <OperationContract Name="HelloWorld">
  <OperationArgument Name="input" Type="p:String" />
  <OperationArgument Direction="Out" Name="result1" 
   Type="p:String" />
  </OperationContract>
</ServiceContract>

You do the XML contract first, then do the logic for it. Except - the logic can be in XML too!

DynamicActivityAction 
 xmlns="clr-namespace:System.WorkflowModel;
 assembly=System.WorkflowModel">
 <DynamicActivityAction.InVariables>
  <Variable x:Name="op1" x:TypeArguments="p:String" />                
 </DynamicActivityAction.InVariables>
 <DynamicActivityAction.OutVariables>
  <Variable x:Name="HelloWorldResult" 
   x:TypeArguments="p:String" />
 </DynamicActivityAction.OutVariables>

But not exactly - you are actually pointing it to a Workflow block. So all your logic goes into WF which you'll need to create somewhere.