Saturday, 24 April 2010

Hi all

As many of you know, I am writing this book on BizTalk along side some great names of the community.

Anyway, I was just writing about the Scope shape for orchestrations and decided to go through the documentation of this to see if I missed something. And indeed there was a small detail I missed, which you can find at – it states that “You can nest scopes up to 44 levels deep.”

I thought that was a funny number and decided to test it.

So I started adding Scope shapes and at 19 nested Scope shapes I had this:


which looks just fine. BUT, after adding an expression shape to the content of the 19’th Scope shape and adding the 20’th Scope shape I get this:


which is not fine.

So basically, the orchestration designer will not show you the Scopes at level 20 or deeper. You can still add them, though – and it compiles just fine even at 47 levels of Scope shapes, actually – haven’t bothered trying more levels than that.

Now, some of you (all of you?) may sit and wonder: Come on, how probable is it that anyone will do that? An I completely agree – if you get above 10 levels of nested Scope shapes you are most definitely going in the wrong direction :) I just wanted to see if the documentation was correct on this.

I hope this will help someone, but it probably won’t :)


Saturday, 24 April 2010 11:48:05 (Romance Daylight Time, UTC+02:00)  #    Comments [4]  | 
Monday, 26 April 2010 17:49:21 (Romance Daylight Time, UTC+02:00)
Oh, Jan....oh, Jan :-)
Monday, 26 April 2010 20:29:52 (Romance Daylight Time, UTC+02:00)
Hi Charles.

Yes, I know... I know... :) I'll get a life as fast as I can - promise! :)

Anyway, funny that they explicitly state the number 44 in the documentation when it clearly doesn't apply...

I appologize for the inconvenience :-)

Wednesday, 28 April 2010 14:22:24 (Romance Daylight Time, UTC+02:00)
First of all, very funny! Though I'm already thinking of the client to whom I'm going to have to explain that just because you can do it doesn't mean you should.

Second, I have noticed some oddities using the Scope shape in orchestrations with VS 2008/BT 2009. Things such as when I try to move the scope it won't move, but if I close the project and then open the project (the old BizTalk standby) the scope is now in the correct spot. You may find that your scope appears if you close and reopen your project.

Saturday, 08 May 2010 09:08:00 (Romance Daylight Time, UTC+02:00)
Hi Elisabeth

Tried closing and opening up the solution. That didn't work. Actually, VS.NET crashes for me when I try to open that orchestration :-(

All comments require the approval of the site owner before being displayed.
Please login with either your OpenID above, or your details below.
Home page

Comment (Some html is allowed: a@href@title, b, blockquote@cite, em, i, strike, strong, sub, sup, u) where the @ means "attribute." For example, you can use <a href="" title=""> or <blockquote cite="Scott">.  

Enter the code shown (prevents robots):

Live Comment Preview

Theme design by Jelle Druyts