.NET 4.5 has introduced some great new features to improve the usability of the Workflow designer. If you’re rehosting the designer outside of Visual Studio then you can take advantage of most of these features very easily which is what I have done with Workflow Studio. If you’ve read my...

Rehosting the WF designer in an application outside of Visual Studio is nothing new and since WF4, nothing particularly difficult. In fact the WF product team has gone out of its way to make rehosting the designer as easy an experience as possible and they’ve done a great job. The WCF and WF Samples...

This article is part of a series: Part 1 Part 2 Inside ExecuteXamlWorkflow In my last post I introduced the ExecuteXamlWorkflow custom activity, an activity that you can use in your own workflows to execute a XAML file based child workflow. You can download the solution here ...

In WF 3.5 it was possible to enable and disable activity execution by simply changing the Enabled property in the designer property grid. This would turn on or off both validation and execution of the activity and was really useful in scenarios where you would want to quickly and easily switch out sections...

This article is part of a series: Part 1 Part 2 Overview Using the WF designer to compose workflows from other workflows is trivial providing the child workflow has been compiled. Then it’s simply a case of drag and drop. But what about the scenarios where at design time...

If you've ever spent any time developing business rules in Windows Workflow Foundation using the RuleSetDialog then you'll have very quickly become infuriated with its inability to resize. The "letterbox" view of if/then/else expressions that allows for a maximum of three lines of text becomes...