Comments

# Ryan CrawCour said on February 2, 2010 08:46 PM:

so i got stuck on the "not available in the same project" point.

wonder what's with that? that's kind the point ... it compiles in to the dll, so why can't i use it?

Must be some obscure reason for it; perhaps you could ask the product team when you attend the MVP Summit! I'd love to know. Me thinks they never planned for this, and it kinda just happened.

# wmmihaa said on February 2, 2010 09:28 PM:

I will check up on this issue ;)

# Jan Eliasen said on February 13, 2010 11:43 AM:

Hi Ryan and Mikael.

Well, as I see it, when shifting to BizTalk 2009, they made some changes to the VS.NET model, mainly that they made BizTalk proejcts specialized C# projects as opposed to the old BizTalk-only projects. This had the side effect that you could suddenly add .CS files, but really; They never thought this through. With all the many many many really angry BizTalk developers out there struggling with issues in these new proejcts, like references getting lost and whatnot... It was a shift that they made WAY too fast, and as mentioned, they never thought it through. We cnaonly hope that they will do something about that in the future.

# Yossi Dahan said on February 19, 2010 02:04 AM:

I would also bet on this changing in the future.

This is really only due to the fact hey never updated the type picker code and - as previously there was no chance a useful class could exist in a BizTalk project, the type picker simply ignores those!

Leave a Comment

Title (required) 

Name (required) 

Your URL (optional)

Comments (required) 

Remember Me?