I'll cross post for awhile to this blog; however, I'm now also posting on the Wintellect blog site at http://www.wintellect.com/c

Workflow Foundation (WF) catches the unhandled exceptions of any workflow instance that it’s charged with running. Upon catching the unhandled exception of a workflow instance, WF terminates it and raises a WorkflowTerminated event where it generously includes the exception in the event arguments. At first glance this seemed like a reasonable approach. After all, one doesn’t want a sloppy and poorly crafted workflow taking down an entire service and jettisoning hundreds of other smoothly executing...

The Business Rules Engine of Windows Workflow Foundation does not appear to update value type fields that are part of a structure. When the THEN action of a rule is executed and a calculation updates a value type in a struct, the value of the structure member remains zero. Turning on tracing of the execution of individual business rules shows successful execution of the assignments, but the targeted field maintains its initial value of zero during its use in subsequent calculations. No exceptions...

It appears that console hosted Windows Workflow applications hang and CPU usage climbs to 100% when executing the CreateWorkflow method from program.cs when Mailframe's Testrunner is installed on the same machine. Testrunner is a Visual Studio add-in that integrates running NUnit tests and provides test performance and coverage metrics (good when a project's unit tests were previously written with NUnit, or you don't have or wish to purchase a VSTS license). Removing Testrunner seems to fully resolve...

Microsoft Corporate V.P. Developer Division Soma Somasegar announced today on his blog that the WinFX name will be officially changed to .NET Framework 3.0. Windows Workflow Foundation will also be a part of the .NET 3.0 Framework.