I have to give kudos to the ASP.NET Team. I really love the Atlas programming model. I'd like to tell you that my Atlas based Workflow Designer is ready - but it isn't. But - I did re-build the WF WorkflowMonitor sample application tonight as an ASP.NET Atlas based application (oh - and I also did is as a non-Atlas based ASP.NET application for those of you that are still suck doing flicker-based PostBacks ;-)). What is Workflow Monitor? Well the Windows Workflow Foundation runtime will take advantage of a TrackingService - if one is found inside of the WF runtime. The runtime ships with a SqlTrackingService - which by default tracks all Activity events. See my post on the WF forums if you have never gotten tracking up and running for the steps I think people should go through to get the zen of WF tracking - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=438583&SiteID=1 . One of the coolest steps is to use the Workflow Monitor sample that ships with the WF SDK. It is a Windows Forms application that will (assuming you are using the SqlTrackingService and have added your workflow assembly as a reference or into the directory where Workflow Monitor is running) show you what has executed in terms of your Workflows. If you set the SqlTrackingService.IsTransactional property to false, you can even see this in semi-realtime as the SqlTrackingService will write each event to the database as it happens rather than batch them (all writes are done transactionally regardless of Read More...