Browse by Tags

• 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... Posted Wednesday, May 30, 2007 6:04 PM from Jon Flanders' Blog | (Comments Off) Filed under: BizTalk;BizTalk 2006

• BizTalkGenerateStrongName Redux

  I've been traveling the world (ok technically traveling to Redmond, London or Dublin) teaching BizTalk Server 2006 R2 training. I have some interesting posts planned around the technology in R2 - this post is about a tool I built quite a while ago - and that Carlos Medina improved. I've been doing demos around BizTalk and one of the tedious things I find when developing with BizTalk is that there isn't anyway to "auto-sign" a BizTalk project. If you've ever seen me demo BizTalk - I always at some point create a BizTalk project - and I have a tool under the Tools menu in Visual Studio which autogenerates a .snk file and puts in the proper path to that file in my project settings. Another thing I've done since building that tool is work alot with vsi files in Visual Studio (template files) which allow you to package up a addin, template, or macro into a nice easy to install package. So here is the latest BizTalkGenerateStrongName code as well as a vsi. Just download and double-click the vsi - and you should get a new tool the next time you open Visual Studio. Highlight your BizTalk project in the solution explorer - then hit the BizTalkGenerateStrongName command under the Tools menu. Enjoy. BizTalkGenerateStrongName1.zip (60.61 KB) biztalkgeneratestrongname.vsi (19.88 KB) Read More... Posted Tuesday, April 24, 2007 4:14 AM from Jon Flanders' Blog | (Comments Off) Filed under: BizTalk;BizTalk 2006