Windows Workflow Foundation
Hi Rahul,
Did you take a look at the following sample : http://msdn2.microsoft.com/en-us/library/ms741709.aspx
Some other possible solutions that came to my mind :
You can have your workflow to have a global property on which you can set the values, if you dont want your workflow to have a property then try the following:
You can have an attached dependency property on the receive activity that will be attached on the workflow and you may be able to pass the values like that. When it is set on the activity, it will actually be set on the workflow.
You can hold it in your host, and everytime you can get the value from the host, set it and send the value back to host.
If none of these work for you let me know and i can try to come up with more solutions
Elif
Hi Rahul,
Here is some read on it:
http://msdn2.microsoft.com/en-us/library/system.workflow.componentmodel.dependencyproperty.aspx
I believe when you use the RegisterAttached method you wont have trouble in passing the value over since the owning activity will nto be the custom activity for that property.
I currently could not find a sample among our sdk samples however i will keep lookin in the netfx3 site and let you know of the sample applications that use regfisterattached.
Hope this works
Elif