Schema References broken in Orchestration

Question

Hello Guys,

We use BTS2009 and VS08.

We often experience very strange behavior in regard to references to other projects.
We have several projects containing schemas. This is whats going on:
1. We add a project reference to our orchestration project.
2. We build and deploy. Everything is fine.
3. Going back to visual studio suddenly the references to our schema projects are no longer valid. A lot of items in the orchestration view become invalid. build is no longer possible. We did not (consciously) change anything in the meantime...
4. We clear the reference, add it again and change all the schema references and it works again....until....
...continue with step 3....

We decided to put all our schemas in the same project, although this is a solution we do not like at all....


Does anybody have an explanation for this strange behavior? I heard a best practice is to put some of the schemas into separate project. We can not do this with the problems mentioned above. Do you reference schemas in other assemblies in your projects without these issues?

many thanks and regards

Manuel

Answer 1

I face some problem sometimes in other project, mostly it happens if the referenced library hasn't build correctly. Batch Build helps me on this.

---

Thanks. Mo

Answer 2

Hi,

You can try this: http://support.microsoft.com/kb/977428/en-us

---

HTH,

Randal van Splunteren - MVP, MCTS BizTalk Server
http://biztalkmessages.vansplunteren.net

Please mark as answered if this answers your question.

Check out the PowerShell provider for BizTalk: http://psbiztalk.codeplex.com

Answer 3

Hi Manuel,

A hotfix for BizTalk 2009/VS 2008 has just been released: http://support.microsoft.com/kb/977428/en-us. This may resolve your issue.

Cheers,

Steef-Jan Wiggers (http://soa-thoughts.blogspot.com/).

If this answers your question please mark it accordingly it would be much appreciated. 

---

BizTalk Server

Answer 4

Wow!

Thanks for the fast answers. I will check out the hotfix in the next days and let you know about the results...

Many Thanks!

Answer 5

Now that's one famous hotfix :)
It will very likely fix your issue.

---

Thiago Almeida - http://connectedthoughts.wordpress.com

Answer 6

Hi!

I have the same problem as Manuel in the same environment (BTS2009 and VS08).
Additionally when I try to set a message type by <Select from referenced assembly...> to a schema whose origin is in a referenced project I can't do it because there is no listed assembly I could choose the desired schema..

Another problem is that I'm not able to validate a schema that has includes to other referenced schemas...

Does anybody have an idea how I could solve these issues?

Thank you very much!

Answer 7

Hello Guys,

We use BTS2009 and VS08.

We often experience very strange behavior in regard to references to other projects.
We have several projects containing schemas. This is whats going on:
1. We add a project reference to our orchestration project.
2. We build and deploy. Everything is fine.
3. Going back to visual studio suddenly the references to our schema projects are no longer valid. A lot of items in the orchestration view become invalid. build is no longer possible. We did not (consciously) change anything in the meantime...
4. We clear the reference, add it again and change all the schema references and it works again....until....
...continue with step 3....

We decided to put all our schemas in the same project, although this is a solution we do not like at all....


Does anybody have an explanation for this strange behavior? I heard a best practice is to put some of the schemas into separate project. We can not do this with the problems mentioned above. Do you reference schemas in other assemblies in your projects without these issues?

many thanks and regards

Manuel

It is better for the answer, I wonder if you can explain your needs more clearly.