CodePlex

Home
Releases
Discussions
Issue Tracker
Source Code
Stats
People
License
 
Comments | Print View | Page Info | Change History (all pages)
Search Wiki:
Home

Overview

The Microsoft ESB Guidance provides architectural guidance, patterns, practices, and a set of BizTalk Server and .NET components to simplify the development of an Enterprise Service Bus (ESB) on the Microsoft platform and to allow Microsoft customers to extend their own messaging and integration solutions.

image001.jpg

Status

The ESB Guidance released on November 8, 2007! Please see the official ESB Guidance page on MSDN for more information about its contents, intended audience, design goals, and to download the complete ESB Guidance (source code, samples, and documentation).
You can download the final CHM version of the documentation here.

PowerPoint Presentations



Future Plans


Our team started working on the next release of ESB Guidance for Microsoft BizTalk Server 2006 R3. The version 2 release date will coincide with BizTalk 2006 R3 release.
Last edited Fri at 7:37 PM  by dmitrio, version 14
Comments
nakulbhagat wrote  Jun 18 2007 at 9:05 PM  
Hi. I want to know if there are any possibilities that ESB can help in retrieving the details of executing substates within the Parent Orchestration and Child Orchestration. It seems the ESB gets confused when a segment index from Child Orchestration is returned. ESB uses that index to find segment in Parent Orchestration and eventually throws an IndexOutOfRange Exception. Can anyone help on this or has some suggestions?

martywaz wrote  Jun 25 2007 at 12:14 AM  
Yes....I fixed that in this CTP drop. Within the docs, you'll find a fairly substantial list of bug fixes, and some feature additions.

nakulbhagat wrote  Jun 25 2007 at 8:10 PM  
Thanks!! But, I found the solution for that too. Now I am facing another problem. While using the Exception Management Component in scenario where two orchestratons are called simultaneously using the parallel shape, Exception Component fails in one of them and throws an CreateFaultMessageException. If I call orchestrations sequencially, it works perfectly fine. I am not getting what must be the problem. Is it because of serialization?

nakulbhagat wrote  Jun 29 2007 at 3:40 PM  
Hey I found the answer for this one too, I am getting too impatient to find an answer :) . Thanks a lot!!

ifergus wrote  Mar 11 at 10:17 PM  
The guidance provided makes no reference to Connected Services Framework (CSF). Does CSF play an integral part of the future for SOI or has it be usurped by advances to BizTalk and .NET 3.*?

NISHIL wrote  Mar 29 at 2:58 PM  
Mr BHagat, PLease be patient or else you might need an doctor's appoinment soon.......Hope America is treating you well....God bless Jeorge Push.....Heyyy I heard tht name somewhr

Sign in to add a comment

Current Release

ESB Guidance - Novembe...
Thu Nov 8 2007 at 8:00 AM

Activity

7 30 All days
Page Views
2162
Visits
797
Pages Per Visit
2.71
Work Items Closed
0
Discussion Posts
1
© 2006-2008 Microsoft | Privacy Statement | Terms of Use | Code of Conduct | CodePlex Blog | Version 2008.5.27.12860
Updating...