Most of the time in software when we say “Parallel” we mean that multiple threads are being used to do work concurrently.  Because of this, many customers ask if the Parallel activity works this way in Windows Workflow Foundation.  I know there is a great deal of confusion about activities and threads and in the next few posts I hope to bring some clarity. Activity Lifecycle Phase 1: Scheduling Activities are scheduled by a parent activity (or the Workflow Runtime if they are the root activity...

If you want to read the AppFabric Monitoring Database from a Web Application your web app will have to have permission to login. If you try to run a web app that does not have permission you will likely see this Cannot open database "AppFabricMonitoringDB" requested by the login. The login failed. Login failed for user 'IIS APPPOOL\DefaultAppPool'. You have two choices. Run the Web Application in an AppPool using an identity that has permission to login Grant permissions to the...

If you are a C# developer using Workflow you might not know how VB does type conversion. Imagine this simple example.  I’ve got some classes which use inheritance 1: public abstract class Shape 2: { 3: public int Top { get; set; } 4:   5: public int Left { get; set; } 6: } 7:   8: public class Circle : Shape 9: { 10: public int Radius { get; set; } 11: } 12:   13: public class Square : Shape 14: { 15: public int Length { get; set; } 16:   17: public int Width { get; set;...

One of the problems with the current version of Windows Workflow Foundation is how to handle different versions of your workflows. With short running workflows this is no big deal, workflows do whatever they are supposed to do and finish, and you can deploy a newer updated version of your XAMLX files whenever you want. Provided the public facing SOAP interface doesn’t change no one will notice a difference and everything will work just fine. However as soon as we get into long running workflows and...

I can’t count how many times this has bitten me…  You create a new Workflow Service.  You create a client app, add a service reference and boom! There is no context attached to the incoming message for the service and the current operation is not marked with "CanCreateInstance = true". In order to communicate with this service check whether the incoming binding supports the context protocol and has a valid context initialized. For some strange reason, our default Workflow Service...