Welcome to Windows Workflow Foundation (WF)
Top Tasks :

WF Community Bloggers

Orchestration performance

So I had to fire up my XP laptop today because my new Rode Podcaster microphone (which is otherwise is totally awesome) won't start on Vista despite getting a usbaudio.sys hotfix from MS Support (which was a suprisingly painless experience). Anyway - cleaning out my old harddrive I found this picture: This is a picture of the BAM portal. What I was doing was using BAM to give me some rough performance metrics between two version of an orchestration. In the "XmlDocument" version of the orchestration I was reading in a 9MB Xml file into BizTalk. In the orchestration I was passing the document to a .NET component as "XmlDocument" and reading the whole document. This is the typical example code you'll find for reading BizTalk messages from .NET code. In the "XmlReader" version of the orchestration - I was passing the message as XLANGMessage. This is the underlying datatype that the Orchestration compiler uses to represent a message. Only when you pass it to a .NET component as XmlDocument do they actually convert it to an XmlDocument (even if your message type on your orchestration is System.Xml.XmlDocument btw). Inside of the method my code looked something like this: public static XmlDocument FromMsg(XLANGMessage old) { //get at the data XmlDocument ret = new XmlDocument(); XmlReader reader = (XmlReader)old[0].RetrieveAs( typeof (XmlReader)); //construct new message from old //read property object msgid = old.GetPropertyValue( typeof (BTS.MessageID)); return ret; } By calling RetrieveAs Read More...
Published Wednesday, May 30, 2007 6:04 PM by Jon Flanders' Blog
Anonymous comments are disabled

<May 2007>
SuMoTuWeThFrSa
293012345
6789101112
13141516171819
20212223242526
272829303112
3456789

Copyright © 2006 Microsoft Corporation. All Rights Reserved. | Terms of Use | Privacy Statement | Contact Us