BizTalk Project References Misbehaving

I have an orchestration that calls another orchestration passing to it a message as an argument. The second orchestration sends the message. These are BizTalk ’04 orchs. I upgrade them to BizTalk ’06 using VS 2005. I also modified the message used by the new orchs slightly. The new orchs work fine by themselves, but when I try to run the old orchs side-by-side the new, the new first orch wants to call the second old orch. I’ve double-checked the project to make sure that the new orch is, in fact, referencing the only the new second orch. Is there a config file that gets written to … much like in .NET web.config where <assembly> keys get generated? (e.g.<add assembly=”System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089″/>)