I have been trying to make a call to orchestration B from within another
orchestration A.  I had  hoped to make the calls to B from various other
orchestrations also -  I had tried to build B and then add this as an
existing item (ie project) to A and when I included the call orchestration
shape in A I could not find any reference to B as an orchestration that I
could call.

The only way around this was to add each item (4 in total ) to the project
that I had defined A in and then I had to change some Namespace values in
project A that referred to project B.  This works OK but if I have multiple
orchestrations to do this to and I make a change to B then I will have to
echo that change through all the orchestrations.

Speccifically B is an email orchestration that i would like to reuse by
passing in parameters from A and the others orchestrations, C, D etc

I hope that is not too confusing.

[ Post a follow-up to this message ]

To effectively reuse "b", you want to be compiling "b" into a distinct
assembly that is referenced by assemblies that contain "calling"
orchestrations -- just like reusing other components or libraries.
(And, as is standard vs.net practice, use "project references" if "a" and
"b" are in the same solution.)

- Scott Colestock


"Neil Hewitt" <NeilHewitt@discussions.microsoft.com> wrote in message
news:B51E58A7-3CB8-4310-9C40-19C9CCA311E7@microsoft.com...
>I have been trying to make a call to orchestration B from within another
> orchestration A.  I had  hoped to make the calls to B from various other
> orchestrations also -  I had tried to build B and then add this as an
> existing item (ie project) to A and when I included the call orchestration
> shape in A I could not find any reference to B as an orchestration that I
> could call.
>
> The only way around this was to add each item (4 in total ) to the project
> that I had defined A in and then I had to change some Namespace values in
> project A that referred to project B.  This works OK but if I have
> multiple
> orchestrations to do this to and I make a change to B then I will have to
> echo that change through all the orchestrations.
>
> Speccifically B is an email orchestration that i would like to reuse by
> passing in parameters from A and the others orchestrations, C, D etc
>
> I hope that is not too confusing.
>

[ Post a follow-up to this message ]

if i understand what you are saying should i be adding B as a reference to A
using the solution explorer and right clicking on the reference under A, and
adding B as a referenced project  or assembly ?

i tried both of these methods ie adding a referenced project and a
referenced assembly with no luck.  After I added the b.dll to the  project
containing the orch A definition  - i double clink the Call shape in order t
o
set up the call to B - i get the message :-

"There are no available BizTalk Orchestration to call.  A callable
orchestration is one that does not have an initial Receive shape with its
'Acticate' property set to True.

i thought that if i added the project where the B orchestration is defined
then i would be able to call B from A .. this does not seem to be the case ?

Am i missing something.

Thanks,

Neil

"Scott Colestock" wrote:

> To effectively reuse "b", you want to be compiling "b" into a distinct
> assembly that is referenced by assemblies that contain "calling"
> orchestrations -- just like reusing other components or libraries.
> (And, as is standard vs.net practice, use "project references" if "a" and
> "b" are in the same solution.)
>
> - Scott Colestock
>
>
> "Neil Hewitt" <NeilHewitt@discussions.microsoft.com> wrote in message
> news:B51E58A7-3CB8-4310-9C40-19C9CCA311E7@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

you have to make the orchestration in your called assembly (b here I think)
public so it is accessible outside of its assembly.

Matt


"Neil Hewitt" <NeilHewitt@discussions.microsoft.com> wrote in message
news:74C8D3BC-80BC-476F-AA01-A78C2D2B4C7F@microsoft.com...[vbcol=seagreen]
> if i understand what you are saying should i be adding B as a reference to
> A
> using the solution explorer and right clicking on the reference under A,
> and
> adding B as a referenced project  or assembly ?
>
> i tried both of these methods ie adding a referenced project and a
> referenced assembly with no luck.  After I added the b.dll to the  project
> containing the orch A definition  - i double clink the Call shape in order
> to
> set up the call to B - i get the message :-
>
> "There are no available BizTalk Orchestration to call.  A callable
> orchestration is one that does not have an initial Receive shape with its
> 'Acticate' property set to True.
>
> i thought that if i added the project where the B orchestration is defined
> then i would be able to call B from A .. this does not seem to be the case
> ?
>
> Am i missing something.
>
> Thanks,
>
> Neil
>
> "Scott Colestock" wrote:
> 

[ Post a follow-up to this message ]

how exactly do i go about that ?

"Matt Milner" wrote:

> you have to make the orchestration in your called assembly (b here I think
)
> public so it is accessible outside of its assembly.
>
> Matt
>
>
> "Neil Hewitt" <NeilHewitt@discussions.microsoft.com> wrote in message
> news:74C8D3BC-80BC-476F-AA01-A78C2D2B4C7F@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

i am not sure how to make an assembly public ?   can someone help ?

"Neil Hewitt" wrote:
[vbcol=seagreen]
> how exactly do i go about that ?
>
> "Matt Milner" wrote:
> 

[ Post a follow-up to this message ]

If you want to be able to use an Orchestration, that is referenced, the
referenced Orchestration need to be public.  To make it public on the
properties for the Orchestration, look for Type Modifier.  Make that Public,
then recompile and deploy, and it should be callable from any other Project,
as long as the assembly with this orchestration is referenced.

A second option, which we use for some of our projects, is to use a MSMQT
Receive Location to start the Orchestration.  One big adavatage, and the
reason we do this, is that other applications and not just Biztalk can use
the Common Flow.  The big disadvatage is that all information being passed
in and being received from the flow, has to be emmbedded in the XML, and not
as Orchestration Parameters.

Todd

"Neil Hewitt" <NeilHewitt@discussions.microsoft.com> wrote in message
news:882903C4-9BE8-45B0-8212-8EC696FF2BEB@microsoft.com...[vbcol=seagreen]
>i am not sure how to make an assembly public ?   can someone help ?
>
> "Neil Hewitt" wrote:
> 

[ Post a follow-up to this message ]