How to set bindings for generic properties of custom activity in workflow foundation?

I've been doing some additional work in this area as my previous answer, although technically usable isn't really ideal. So I've come up with a better solution Basically, when binding properties, the built in designer 'guesses' as to which control to load up when you click the ellipsis in the property box. When you point it to a list, it loads up some fancy editor that lets you manually add list items, which is basically useless for any sort of dynamic data scenarios I did some digging and tripped across this post: blogs.microsoft.co.il/blogs/bursteg/arch... It wasn't exactly what I needed, but it did clue me in to the Editor attribute The 'what do I need to know' part of this answer is here, simply add this attribute to your property declaration (the actual property, not the DependencyProperty backing field): Editor(typeof(BindUITypeEditor), typeof(UITypeEditor)) That will force the GUI to load up the dependency property binding interface This isn't really a shortcoming of the workflow framework itself, but it was kind of annoying to have to dig into this so deeply to figure out the solution.It just seems everywhere you turn with windows workflow, the questions are there but not the answers Anyways, I hope this helps you or someone else if you run into this issue.

I've been doing some additional work in this area as my previous answer, although technically usable isn't really ideal. So I've come up with a better solution. Basically, when binding properties, the built in designer 'guesses' as to which control to load up when you click the ellipsis in the property box.

When you point it to a list, it loads up some fancy editor that lets you manually add list items, which is basically useless for any sort of dynamic data scenarios. I did some digging and tripped across this post: blogs.microsoft.co.il/blogs/bursteg/arch... It wasn't exactly what I needed, but it did clue me in to the Editor attribute. The 'what do I need to know' part of this answer is here, simply add this attribute to your property declaration (the actual property, not the DependencyProperty backing field): Editor(typeof(BindUITypeEditor), typeof(UITypeEditor)) That will force the GUI to load up the dependency property binding interface.

This isn't really a shortcoming of the workflow framework itself, but it was kind of annoying to have to dig into this so deeply to figure out the solution. It just seems everywhere you turn with windows workflow, the questions are there but not the answers. Anyways, I hope this helps you or someone else if you run into this issue.

I just ran into this same issue and I solved it by simply eliminating the need for the collection. You could do the same pretty easily: public class Parameters { private Dictionary _parameters; public void Add(string name, string value) { _parameters. Add(name, value); } } You can then bind that to your dependency property instead of the list.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.