Feb 082011
 

Quite a few people have asked “What are sequental convoys?” and “When should I use them?”.  So here is the definition and a quick example on when and/or how I would use them. 

 “A sequential convoy enables multiple single messages to join together to achieve a required result. A sequential convoy is a set of related messages that have a predefined order. Although the messages do not have to be exactly the same, BizTalk Server must receive them in a sequential order.” * Microsoft definition

 Where this becomes handy in business is around batching of messages, an example of this would be when a business process requires batch processing that needs to retain the order in which the message was received.  The way this is accomplished is to put a Listen shape within a delay, which the delay the loop ends.  During this delay time any number of received messages can enter the same business process.  This approach can have a side effect of Zombie messages, but we will look at those in a future post.

In our book, we discuss a pharmaceutical ESB system and we have a process that batches order messages from vendors until 2pm, then sends order processing and shipping.  In this process we show the use of sequential convoys as well as look into the side effects of this process.

Jan 182011
 

Printing in Silverlight has been made pretty simple, how it comes with some caveats because it opnly supports rasterized image printing.  Not 100% a problem but in LOB applications will run into issue with printing thinks like PDF, because all formatting is lost in reflect to the final printed document.

Here is a quick code method on printing in Silverlight 4:

[sourcecode langauge="csharp"]
PrintDocument documentToPrint= new PrintDocument();
documentToPrint.DocumentName = "Sample Document";
documentToPrint.StartPrint += new EventHandler(documentToPrint_StartPrint);
documentToPrint.PrintPage += new EventHandler(documentToPrint_PrintPage);
documentToPrint.Print();
[/sourcecode]

Jan 062011
 

The Life Cycle of a page when requested for the first time:

Initializing: During this phase, the server creates an instance of the server control

Loading: During this phase, the instance of the control is loaded onto the page object in which it is defined.

PreRendering: During this phase, the control is updated with the changes made to it. This prepares the control for rendering.

Saving: During this phase, the state information of the control is saved. For example, if a value is set for the control during the Load event, it is embedded in the HTML tag that will be returned to the browser.

Rendering: During this phase, the server creates the corresponding HTML tag for the control.

Disposing: During this phase, all cleanup tasks, such as closing files and database connections opened by the control are performed.

Unloading: During this phase, all cleanup tasks, such as destroying the instances of server control are performed. This is the final event in the life cycle of a server control

The processing sequence in which a page is processed during a postback event is:

Initializing: During this phase, the server creates an instance of the server control

Loading view state: During this phase, the view state of the control posted by the client is reloaded into the new instance of the control.

Loading: During this phase, the instance of the control is loaded onto the page object in which it is defined.

Loading the postback data: During this phase, the server searches any data corresponding to the control that is loaded in the data posted by the client.

PreRendering: During this phase, the control is updated with the changes made to it. This prepares the control for rendering.

Saving state: During this phase, the change in the state of control between the current request and the previous request of the page is saved. For each change, the corresponding event is raised. For example, if the text of a textbox is changed, the new text is saved and a text_change event is raised.

Rendering: During this phase, the server creates the corresponding HTML tag for the control.

Disposing: During this phase, all cleanup tasks, such as closing files and database connections opened by the control are performed.

Unloading: During this phase, all cleanup tasks, such as destroying the instances of server control are performed. This is the final event in the life cycle of a server control

The events associated with the relevant page cycle phases are:

  • Page Initialization: Page_Init
  • View State Loading:LoadViewState
  • Postback data processing: LoadPostData
  • Page Loading: Page_Load
  • PostBack Change Notification: RaisePostDataChangedEvent
  • PostBack Event Handling: RaisePostBackEvent
  • Page Pre Rendering Phase: Page_PreRender
  • View State Saving: SaveViewState
  • Page Rendering: Page_Render
  • Page Unloading: Page_UnLoad
Oct 252010
 

When configuring the BAM portal on a x64 Environment you may receive the following error:

Start registering ASP.NET scriptmap (2.0.50727) at W3SVC/2/Root/BAM.
Error when validating the IIS path (W3SVC/2/Root/BAM). Error code = 0×80040154
The error indicates that IIS is in 64 bit mode, while this application is a 32 bit application and thus not compatible.
(Microsoft.BizTalk.Bam.CfgExtHelper.Utility)

To enable the 32-Bit version of ASP.NET run the following command

cscript %SYSTEMDRIVE%inetpubadminscriptsadsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

OR

You can edit the application pool and change the “Enable 32-Bit Applications” flag to True on the Application Pools for BAM.

There is also a KB article on this.

Oct 252010
 

Was another great weekend with the development community, got to meet allot of great people and Maddux had a great time.

Got to present Linq 4.0 and Silverlight LOB this time around and had a great turn out.  Infragistics helped with providing 3 NetAdvantage Licenses for give aways – thanks Infragistics and the winners.

I am now moving my discussions to Line of Business presentations, so that was the last time the Linq 4.0 presentation will be presented.

Again, thanks everyone for coming and thanks to the coordinators.

Oct 112010
 

Unfortunately you are not able to run both side by side; so I would suggest you run 2009 in a VM and test your 2010 project in that if you need downward compatibility.

Remember, BizTalk 2010 is the only version of BizTalk compatible with R2 version of the Microsoft Server 2008 and SQL 2008.  Setup is still roughly the same.

Oct 042010
 

To add Assembly Viewer to the Windows registry

  1. From the Start menu, click Run.
  2. In the Run dialog box, type cmd.
  3. From the command line, navigate to <BizTalk Server Installation Folder>Developer Tools where BTSAsmExt.dll resides.
  4. At the command line, type:

    regsvr32 BTSAsmExt.dll

  5. To begin using Assembly View, log off and then log back onto the computer.

To remove Assembly Viewer from the Windows registry

  1. From the Start menu, click Run.
  2. In the Run dialog box, type cmd.
  3. From the command line, navigate to <BizTalk Server Installation Folder>Developer Tools where BTSAsmExt.dll resides.
  4. At the command line, type:

    regsvr32/u BTSAsmExt.dll

  5. To complete the removal, log off and then log back onto the computer.