January, 2010

In my last post , I covered using ActivityAction in order to provide a schematized callback, or hole, for the consumers of your activity to supply.  What I didn’t cover, and what I intend to here, is how to create a designer for that. If you’ve been following along, or have written a few designers using WorkflowItemPresenter, you may have a good idea how we might go about solving this.  There are a few gotcha’s along the way that we’ll cover as we go through this. First, let’s familiarize...

Scenario: A BA starts with the Workflow authoring using the Re-hosted workflow designer and the Toolbox activities provided in the palette. At some point, the BA figures out that the Toolbox doesn't contain an activity that he is looking for. Only option that the BA has for him is to work offline with the Dev to add such an activity to the Toolbox palette. Loss of considerable amount of time, every time the BA figures out that the activity he needs is not present. Wouldn't it be nice, if...

In the series, the next question we generally get is, How about Validations. How can I have one set of validations for Devs in VS only and another set for BAs in a non-VS environment. To demonstrate that, again I have developed it on top of the sample application we saw in the previous post. In here, to know that I am in the VS environment, I am assuming that the designer used would be from CustomActivities.VisualStudio.Design.dll. Next, I override OnModelItemChanged and set the property for the...

One of the selling points with Workflows is customers have been able to customize the Workflows and can have a collaborative work between the BAs and Developers. BAs define the business process using the Re-hosted Workflow designer and the dev fine tunes/completes the implementation by taking the Workflow file in VS and editing it as appropriate. In that context, the very first question that generally comes is, for a particular activity, how can we have a specific designer for BA and a different...

In the re-hosted scenario, as part of customizations that domain specific users want – we have been asked many times as to how can we not show the toolbar at the bottom of the designer or show only specific items in that toolbar? Internally we refer to it as the Shellbar as well and the API to go about customizing the toolbar is: this .wd.Context.Services.GetService<DesignerView>().WorkflowShellBarItemVisibility = ShellBarItemVisibility.None; The ShellBarItemVisibility is a enumeration where...

In regards to Toolbox, another common question I get is how can we get the Tooltips and icons for our custom activities. Well, quite simple actually: 1. Description attribute for the Tooltip 2. ToolboxBitmap attribute for the Icon Have both these attributes for your custom activity and once this activity appears in the Toolbox, you would have the tooltip on hover with the description and the icon you added. Of course, this is not just for the code activities, but can also be done for the custom declarative...

One of the very essential services while authoring Workflows is Undo-Redo. Common question asked is, how do we get the service outside of VS, in a re-hosted Workflow scenario. Well, in your re-hosted app(assuming it is WPF), it would be: Add the following command bindings: <Window.CommandBindings> <CommandBinding Command= "ApplicationCommands.Undo" Executed= "CommandBinding_UndoExecuted" /> <CommandBinding Command= "ApplicationCommands.Redo" Executed=...

In the previous two posts, we talked about the visual view on the Workflow tracking data and how we can have a restricted debugging experience in the re-hosted scenarios. Moving forward, the next question I get from customers - Is there a way I can show some kind of adorner on the designer when it executes a specific activity in addition to the debug adornment? Also, I want these adornments universal for Out of Box as well as Custom Activities. The adorner can be as simple as a check mark saying...

The hosted compiler does something called type coercion. It converts one type to another type using the widening and narrowing conversions specified by the big VB compiler. On the whole, this is very useful functionality. It allows you to strongly type your arguments but still set your Int16 variable to 5 or your string variable to Nothing. Type coercion is especially important for delegate types and lambda expressions. When the compiler encounters a lambda expression, it infers its type as an anonymous...

Expressions created in the WF designer are serialized using square brackets, which is shorthand for VisualBasicValue <T> or VisualBasicReference <T>. For example, drop a WriteLine activity into a Workflow, and set its text to the expression (1+2).ToString (in VB you can omit the brackets after the ToString). Save your workflow, open it in XAML view ( F7 is your friend ). You see the following XAML: < WriteLine Text ="[(1 + 2).ToString]" /> Now not all text that you enter...

When I was at PDC I spent some time with Ed and Ashley of Ed and Ashley’s 5 minute show . They have a video blog with a number of interviews they have conducted with women in the technology. I spoke with them about mentoring, and the clip was recently posted. See Episode 57, Cathy Dumas (PDC09) . Upshot: mentoring works, it retains women in high tech, start early in your career, have goals in mind, mentor often. I talked about an outreach program started by Erin Chapple ( see her video ) where mentees...

Hi, today I gave a talk to our support team about the expression editing feature. Since this is all public facing information, I thought I would post the deck. Some of this information is old hat to regular readers of this blog (especially the overview and programmability bits, which I ported straight from previous blog entries). However there is plenty of new information in there about serialization, literals, assembly loading, namespace management, imports designer. VisualBasic.Settings, and type...

The Enter and Tab keys work a bit differently in the ExpressionTextBox than in the big VB IDE. In the big IDE, Enter and Tab always insert their associated characters. If the IntelliSense completion list is up, Enter selects the item and inserts a new line. We noticed that big IDE behavior does not always make sense in a single line editor. We found that users expected the ExpressionTextBox to behave exactly as a TextBox, especially in the property grid. So we changed the handling of the Tab and...

There are a whole bunch of buttons in the bottom right hand corner of the workflow designer. Here they are: The magnifying glass to the left of the zoom combo box changes the zoom level of the workflow designer to 100%. (Yes this really is a button.) The button to the right of the combo box fits the contents of the current breadcrumb root to your screen. By clicking the magnifying glass, you can easily remove the effect of clicking the Fit to screen button. The final button is for the overview map...

The Workflow designer, like any good Visual Studio component, has many keyboard shortcuts. We are documenting these shortcuts in the MSDN documentation (I’ll post when the docs are available*), but I thought I’d list them here so that they’re available for you to use now. Shortcut Purpose Ctrl+E, A Shows or hides the Argument Designer. Ctrl+E, C Collapses the selected activity in place. Ctrl+E, E Expands the selected activity in place. Ctrl+E, F Connects the selected activities in a flowchart. Ctrl...

In this episode, we turn to the project system. The Workflow Designer, unlike Cider (the WPF editor), does not have a side-by-side design/code view. If you want to close the designer and view the XAML for the workflow, you must close and reopen the document. You will have to live with this for Dev10. It’s kind of a pain to do this via context menu from the Solution Explorer. Fortunately, there is a keyboard shortcut. When in design view, pressing F7 takes you to the code view. When in code view,...

This is the first in an occasional series highlighting some of the least discoverable features of the Workflow Designer. In this episode, we turn to the flowchart. The FlowDecision and FlowSwitch “activity” designers (they’re really items) have this cute little triangle in the top right hand corner. Hover over it, and you see the condition applied to the item. Click it, you can pin the expression to the flowchart so that it is always visible. “But isn’t there some way to pin all the expressions at...

Update 01/20/2009: Since I failed to mention this before I wanted to make something clear about these workflow posts. All information in these posts is based on the knowledge I gained through developing a framework based on Windows Workflow 4.0. I am not a member of the team nor is this information in any way endorsed by the team. In the previous posts we covered one way you could implement a producer-consumer pattern in workflow. This approach used composition and attempted to hide the complexities...

So far we have written ParallelItemScheduler<T> , which is a generic activity that goes dormant and schedules actions based on input via bookmark resumption. We then used this activity to design ProducerConsumer<T> , which takes this idea a little further and provides a generic mechanism for running a producer thread that can pump data into a consumer thread. In the last part of this series we finally have all required building blocks to design our highly efficient and parallel copy directory...

In my previous post I introduced you to NativeActivity and walked through the design and implementation of a class named ParallelItemScheduler<T> . In part 2 of this series we will be utilizing the aforementioned activity to build a new composed activity named ProducerConsumer<T> . Once we have completed this task we will have a framework for building our final activity, CopyDirectory . Building Activities Through Composition Unlike the previous activity, the ProducerConsumer<T>...