May, 2010

Something that I had as a blog post was almost useful to someone. Almost, except for all the rough edges. So here is a second release of the post/code ‘An Activity Designer for InvokeAction<T>’. If you haven’t read it yet, this post will make more sense after having gone through the first one. Two main Issues with the previously released zipped source code 1) It only works when you load XAML which already has a property reference - it doesn’t work when you drag+drop in a new InvokeAction<T>...

Today I’m cheaply recycling yet another perennial forum and mailing list question into a lightweight blog post. Q. How do I use a custom designer for a XAML activity? On a "normal" code activity I use the [Designer(typeof(MyOwnDesigner))] attribute. How could I apply this attribute on a XAML activity? My favorite way to do this is use a 'code-beside’ file. Yes, code-beside .xaml.cs aren’t just for WPF. How to: You should already have an activity XAML file, say MyActivity.xaml Right...

The WF 4 runtime allows you to extract “payload” data from workflow instances as they run. By configuring a workflow to use a tracking profile you configure which instance states, activity states, workflow variables, and workflow arguments get tracked. I created this sample WF tracking profile editor because we didn't ship an official one this year. The first tab lets you select workflow definition agnostic configurations, while the second tab rehosts the WF designer to let you configure variables...

Recently, we upgraded our Team Foundation Server from 2008 to 2010 at work. Long overdue getting rid off some custom TFS Project templates, we were eager to use the new MSF for Agile 5.0 template. Now, we knew on beforehand that we couldn’t just upgrade existing team projects, so we had to come up with [...] Blog Post by: larsw