I am programmatically adding a FlowSwitch<string> activity to a rehosted designer when a user drags a particlar node from a tree alongside the designer.
When the model item is added to the designer, I set the Expression Text Box Value to a custom CodeActivity<string> and configure it based on the drag source.
Based on the context of the drag source I am able to set the properties of said CodeActivity<string> so that on execution it will be able to resolve the value against which the FlowSwitch will execute.
Thus when the FlowSwitch<string> executes, it executes my Activity<string> and the Cases the user has added are evaluated against that result. Beautiful, even though I realise it is not exactly the use case envisaged by Matt Winkler and
co!
If I look at the underlying Xaml I see the following (I have stripped out elements that are superfluous to this discussion):
<FlowSwitch x:TypeArguments="x:String" sap:VirtualizedContainerService.HintSize="60,75">
<FlowSwitch.Expression>
<deas:GetResolvedPropertyValueActivity ActivityType="Task" DisplayName="Risk" PropertyId="RFQFilterRisk" />
</FlowSwitch.Expression>
</FlowSwitch>
Now that is all well and good but looking at the designer it is obviously not very clear to the user what the FlowSwitch is going to evaluate against.
So necessity being the mother of invention I thought I would use the properties of my GetResolvedPropertyValueActivity as a backing store for some additional Attached Properties on the FlowSwitch<string> that I will then use to 1. modify
the "Switch" label of the FlowSwitchDesigner to something a little more meaningful to the user, and 2. make the property id browsable and thus available in the property inspector view.
I thought this would be a shoe-in using AttachedPropertiesService to add the Attached Properties and ModelService to get hold of my custom activity model item but alas no. Adding the Attached Properties is fine but the Find method of the ModelService
returns null! In fact I can find no way to get at those values without parsing the xaml.
My question is: How can I get at those properties on my GetResolvedPropertyValueActivity without having to resort to parsing the xaml?
chruzi
