12-28-04 01:46 AM
You can create variables in your orchestration that are .Net classes. In
expression shapes in the orchestration, you can use these classes like you
would from a C# application. There are some limitations related to
orchestration persistence such as your class must be serializable or be
consumed in an atomic scope; you might need synchronized scopes if you are
working with your variable on different parallel branches; but for hte most
part it is straight forward. Add a reference to your .net assembly, declare
a variable of the right type, in an expression shape, create a new instance
of your variable and start using it.
Matt
"CyberLotus" <CyberLotus@discussions.microsoft.com> wrote in message
news:95FB1F51-3807-4C1B-8E56-08EEAE9ECF9C@microsoft.com...[vbcol=seagreen]
> Hi Matt,
>
> Thanks for the help.
>
> But Now I want my orchestration to call another application. In the sense,
> I'm having a class and my orchestration should be able to call that class
> (without consuming a web service).
> How can I do that?
>
> TIA,
> Lotus
>
> "Matt Meleski" wrote:
>
[ Post a follow-up to this message ]
|