After RoleLink gets the DestinationParty property, it needs to exclude from it the corresponding Send Port. On other hand, only one port from given party may be associated with specific RoleLink. So the collection of SendPorts from Party (BtsCatalogExplorer.Parties[...].SendPorts) used only when the orchestration is binded. Later, when Party resolved comes into play, its ports are not enimerated, but instead the corresponding ports obtained from Orchestration properties (for the operation being performed).

Generally speaking, the classes from Microsodt.BizTalk.ExplorerOM used primarily in administration activities and such a using should be avoided in orchestrations. For example, as for standalone BTS Explorer, the fragment below lists all the parties and its aliases defined with server XXX.

BtsCatalogExplorer exp = new BtsCatalogExplorer();
exp.ConnectionString = "Server=XXX;Database=BizTalkMgmtDb;Integrated Security=SSPI";
PartyCollection coll = exp.Parties;
foreach(Party party in coll )
{
Console.WriteLine("Party - {0}", party.Name);

PartyAliasCollection collAliases = party.Aliases;
foreach(PartyAlias alias in collAliases)
{
Console.WriteLine( alias.Name );
}
}