11-17-05 11:10 PM
I am having a long running orchestration that have an atomic scope. I am not
getting the variable's value that is declared in the orchestration scope
inside the atomic scope....I can't keep the whole thing within the atomic
scope in the logn running orchestration...according to my scenario, in the
atomic scope I am setting the value of variable (declared in orchestration
scope) from the XMDom message using Xml.XmlNode...that's why I had to keep
the atomic scope...
Can any one suggest what might be the problem?
[ Post a follow-up to this message ]
|