ÿþ<?xml version="1.0" encoding="utf-16"?>

<rss version="2.0">

  <channel>

    <title>Biztalk Blogs</title>

    <description>Aggregation of Biztalk related blogs</description>

    <link>http://blogs.msdn.com/kevinsmi/</link>

    <docs>http://backend.userland.com/rss</docs>

    <generator>Syndicated by BlogWave v0.3(Alpha3)</generator>

    <item>

      <title>BizTalk Server 2004 - Database Growth (Corrected)</title>

      <description>&lt;P&gt;&lt;FONT face=Verdana color=#ff0000 size=1&gt;Corrections to my post! (Many thanks to Lee Graber [MS] for the corrections on a Sunday afternoon.)&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana color=#ff0000 size=1&gt;&lt;STRIKE&gt;BizTalk Server 2004 is a SQL Intensive Application! As with any other transactional database application, having a good database maintenance plan is vital. If you have a SQL DBA on your staff, have him (or her) setup a daily or hourly maintenance plan which backs up or at least truncates your transaction logs (as well as backing up all your BTS related databases). If you've deployed BTS2004 in a small scale environment, you can change the SQL &amp;#8220;Recovery Model&amp;#8220; from &amp;#8220;Full&amp;#8220; to &amp;#8220;Simple&amp;#8220; and create a daily Database Maintence Plan using the wizard included with the SQL Enterprise Manager.&lt;/STRIKE&gt;&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana color=#000000 size=1&gt;&lt;EM&gt;"BTS2004 provides supported scripts for backing up BTS databases transactionally. It is important to make sure that all database backups are done transactionally so [MS] provides a sql agent job [called Backup BizTalk Server] in the management database server which uses linked server (if the other dbs are remote) to go to each database in&amp;nbsp;the system and transactionally mark the log. It then takes a backup of all logs and&amp;nbsp;truncates the logs [to control database growth]. All you have to do is&amp;nbsp;enable the job to run and set a couple of parameters. All of this is documented in the help file. Taking a backup of each database by itself is not usefull since you cannot restore them individually always or else you will break transactional integrity." -- Lee Graber&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;The on-line documentation covers this topic pretty well and if I'd read it more thoroughly I'd have found this SQL job. If you look at the &lt;A href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/operations/htm/ebiz_ops_backuprestore_mygu.asp"&gt;database write diagram&lt;/A&gt; in the on-line help, it becomes much clearer why using this SQL job is the only way to back-up your BTS databases. The parameters that Lee talks about are shown below and in the on-line help file.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face="Courier New" color=#006400 size=1&gt;exec [dbo].[sp_BackupAllFull_Schedule] 'd' /* Frequency */, 'BTS' /* Name */, '&amp;lt;destination path&amp;gt;' /* location of backup files */&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;'&lt;B&gt;d&lt;/B&gt;' = daily full backups. You can change this period to hourly (h/H), weekly (w/W), monthly (m/M), or yearly (y/Y). The first time the job is run during a new period, a full backup is performed. &lt;/FONT&gt;&lt;FONT face=Verdana size=1&gt;'&lt;B&gt;BTS&lt;/B&gt;' is the default for Name. '&lt;B&gt;&amp;lt;destination path&amp;gt;&lt;/B&gt;' for the destination path. You must change this to a valid destination such as 'C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP'. The destination path may be local or a UNC path to another server. &lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face="Courier New" color=#006400 size=1&gt;exec [dbo].[sp_MarkAll] 'BTS' /* Log mark name */, '&amp;lt;destination path&amp;gt; ' /* location of backup files */&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana&gt;&lt;FONT size=1&gt;&lt;B&gt;'BTS' &lt;/B&gt;is the default for Log Mark Name. Change as needed. Log Mark Name is part of the naming convention for backup files: &lt;FONT face="Courier New" color=#006400&gt;&amp;lt;Server Name&amp;gt;_&amp;lt;Database Name&amp;gt;_Log_&amp;lt; Log Mark Name &amp;gt;_&amp;lt;Timestamp&amp;gt;&lt;/FONT&gt; and '&lt;B&gt;&amp;lt;destination path&amp;gt;&lt;/B&gt;' for the destination path. You must change this to a valid destination such as C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP'. The destination path may be local or a UNC path to another server.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;&lt;STRONG&gt;MS also makes a few key points to remember on this topic.&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;1. The SQL job does not delete old backup files. You must manage those files to conserve disk space by backing them up and deleting them after new full backups have been created. &lt;FONT color=#ff0000&gt;(I wonder how to automate this?)&lt;/FONT&gt;&lt;BR&gt;&lt;/FONT&gt;&lt;FONT face=Verdana size=1&gt;&lt;BR&gt;2. Do not store the backup files on the same storage system as the database, because in the event of a failure, both the backups and the databases would be lost. &lt;FONT color=#ff0000&gt;(We currently perform disk-to-disk and then disk-to-tape backups for all vital SQL databases.)&lt;BR&gt;&lt;/FONT&gt;&lt;BR&gt;3. It is recommended that you practice restoring your databases at least once a month. Do not wait until your hard disk crashes to see if you can restore your system and databases. &lt;FONT color=#ff0000&gt;(First thing Monday morning on my test server!)&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;HR NOSHADE SIZE="1"&gt;This Blog Hosted On: http://www.DotNetJunkies.com/&lt;img src ="http://dotnetjunkies.com/WebLog/jlynch/aggbug/25021.aspx" width = "1" height = "1" /&gt;</description>

      <link>http://dotnetjunkies.com/WebLog/jlynch/archive/2004/09/09/25021.aspx</link>

      <source url="http://dotnetjunkies.com/WebLog/jlynch/">A BizTalk Enthusiast</source>

      <comments>http://dotnetjunkies.com/WebLog/jlynch/archive/2004/09/09/25021.aspx#Feedback</comments>

      <guid isPermaLink="False">http://dotnetjunkies.com/WebLog/jlynch/archive/2004/09/09/25021.aspx</guid>

      <pubDate>Thu, 09 Sep 2004 10:57:00 GMT</pubDate>

    </item>

    <item>

      <title>BizTalk Server 2004 - Mapping Best Practices #1</title>

      <description>&lt;P&gt;&lt;FONT face=Verdana size=1&gt;&lt;STRONG&gt;Where Do I Put My Maps?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;I get this question all the time and the best answer I've seen comes from &lt;A href="http://blogs.msdn.com/BizTalk_Core_Engine"&gt;Lee Graber&lt;/A&gt;, a veteran BizTalk developer at Microsoft.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;&amp;#8220;While there are actually some performance related reasons to put your maps in the receive and send ports, there are much better business reasons for doing it outside of your schedule. We tend to refer to mapping in receive and send ports as document normalization. In the case of receive ports, you are normalizing the documents from the format of your customers into an internal standard format. On the outbound side, you are converting out of your normalized format and into the specific format of your trading partner or internal application. If you embed the map in the schedule and the partner changes the format, not only do you have to rebuild the map, you have to rebuild the schedule to use the new version of the map. Also, what happens when you add a new partner with a new format. That is a new map and if you have embedded the map in a schedule, it means a new schedule. This is exactly why we added support for multiple maps (one per source message type) on the receive port so that you could create a single location for all of your partners and easily handle normalize into your internal standard formats. Putting these types of maps in schedules would be a bad idea. There are times when it makes sense to use a map in a schedule. When you need to generate a new message in the schedule and use the modified (mapped) contents of an existing message as the base. When you want to map multiple parts of a message into one outbound message (this type of mapping cannot be done in a receive / send port). There are performance gains which come from doing mappings in receive ports sometimes, but they are mostly around how many persisted messages your scenario generates and it is a bit complicated to explain. The actual mapping technology is the same. To keep your internal business logic from getting tightly couple with the document formats of your trading partners, you should do your document normalization (mapping) in the send and receive ports.&amp;#8221;&lt;/FONT&gt;&lt;/P&gt;&lt;HR NOSHADE SIZE="1"&gt;This Blog Hosted On: http://www.DotNetJunkies.com/&lt;img src ="http://dotnetjunkies.com/WebLog/jlynch/aggbug/25011.aspx" width = "1" height = "1" /&gt;</description>

      <link>http://dotnetjunkies.com/WebLog/jlynch/archive/2004/09/09/25011.aspx</link>

      <source url="http://dotnetjunkies.com/WebLog/jlynch/">A BizTalk Enthusiast</source>

      <comments>http://dotnetjunkies.com/WebLog/jlynch/archive/2004/09/09/25011.aspx#Feedback</comments>

      <guid isPermaLink="False">http://dotnetjunkies.com/WebLog/jlynch/archive/2004/09/09/25011.aspx</guid>

      <pubDate>Thu, 09 Sep 2004 09:55:00 GMT</pubDate>

    </item>

    <item>

      <title>Neglect</title>

      <description>&lt;p&gt;Okay, I have been neglect and am trying to remedy this. I have a couple of papers I am working on which will get posted here very shortly. Hopefully one will be here by end of the week. I am also busy at work on BTS stuff trying to make your life easier (I hope). Finally I was away visiting some customers and getting some good real world experience. I have actually visitted lots of customers but it is always good to stay knowledgable because it is too easy to get it the glass ball world over here and forget about everyone who really uses this stuff and the problems they face. Never want to have that happen.&lt;/p&gt; &lt;p&gt;So first off, I just read a write up from Charles Young (who I have now added to my links) on how the subscription routing mechanisms work. Very impressive stuff. He even got some of the sequence of stored procedures being called down. I think it is maybe a bit more technical than a lot of you need, but hey, if you are reading my blog, you must be into this kind of torture, so I would check it out. Good stuff.&lt;/p&gt; &lt;p&gt;Now let's pick a topic to chat about. I have seen some of the other blogs out there and, well, I am sorry mine is not formatted so nicely. Basically you get me at 11:30 pm feeling like I need to shed some insight and just trying to brain dump. So I guess you will bear with me. Hows about debugging routing failures. Not exactly rocket science to the bts experts, but probably a usefull topic.&lt;/p&gt; &lt;p&gt;What is a routing failure: Routing failures occur when messages are published into the messagebox, but no service is found to have expressed interest in the message (ie the properties of the message do not match any subscriptions).&lt;/p&gt; &lt;p&gt;So how do I debug this? -- When a routing failure occurs, the messageagent (see my last post) generates something called a routing failure report. A routing failure report is nothing more than a dummy instance, which holds a reference to a dummy message, which has no parts, but which has the context of the message which failed routing at the time it failed routing. We capture the data like this becomes some adapters do not suspend the message and even when the message is suspended, the context of the suspended message is often different from the context at the time of the routing failure. So what can you do with this. Well really there are only a couple of times routing failures should occur in your system. The first is as you are developing and testing your solution (please test your solution). In these cases you should have a reasonable idea where the message should be going. You can look at the context of the message which failed to route and check which properties were promoted and what their values were. Then, you can use the subscription viewer in the &amp;lt;instsalldir&amp;gt;\sdk\utilites directory to see what the subscripton actually looked like for the sendport or orchestration you thought the mesage should have gone to. Often it is simply that you forgot to promote a property or just got the value in your subscription a bit off. Or you forgot to start the orchestration or sendport.&lt;/p&gt; &lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;The second case where this can occur is when you try stressing a system with orcehstrations which use corelation and you pass in non-unique correlation sets. Don't do this. Try to imagine what is happening with these messages. Now a response which was supposed to go to one orchestration gets broadcast to 20 orchestrations. And then the responses for those find the orchestrations completed and so fail routing. Actually, what would really happen is that half of those 19 would actually get there before the orchestration completed and you might get 9 zombied orchestrations (see earlier blog) and 10 routing failures. Lesson to be leasned, test with real data and in the real world, correlation sets must be unique.&lt;/p&gt; &lt;p&gt;&amp;nbsp;&amp;nbsp; The third case you might get this in some type of stress is also tightly related to zombies (see earlier blog). If you think about it, a zombie is a race condition where the message got routed to the orchestration right before it completed and so you are "completed with discarded messages". Well what would happen if the raec were a bit different. In that case instead of rouitng just before the orcehstration completed, the orcehstration would complete just before the routing happened. Then you would get routing failures. In these cases, this is what you designed the system to do, so I guess you decide what to do with the failed message at this point. Read my blog on zombies to get a better idea of when zombies can happen. &lt;/p&gt; &lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;p&gt;Sorry this was brief, but it is midnight and I'm tired. Like I said, if things work out correctly, I should have a really good blog coming shortly. Just have to get the signoff from Woodgate and a couple of other people. :)&lt;/p&gt; &lt;p&gt;Thanks&lt;/p&gt;&lt;img src ="http://blogs.msdn.com/biztalk_core_engine/aggbug/226674.aspx" width = "1" height = "1" /&gt;</description>

      <link>http://blogs.msdn.com/biztalk_core_engine/archive/2004/09/08/226674.aspx</link>

      <source url="http://blogs.msdn.com/biztalk_core_engine/">BizTalk Core Engine's WebLog</source>

      <comments>http://blogs.msdn.com/biztalk_core_engine/archive/2004/09/08/226674.aspx#Feedback</comments>

      <guid isPermaLink="False">http://blogs.msdn.com/biztalk_core_engine/archive/2004/09/08/226674.aspx</guid>

      <pubDate>Wed, 08 Sep 2004 06:00:00 GMT</pubDate>

    </item>

    <item>

      <title>Download of BizTalk 2004 "Deploy with Nant" Template</title>

      <description>&lt;p&gt;

   &lt;font color=#000000&gt;I see that the GotDotNet workspace I referenced in my last post

   is having occasional trouble, so I'm making the current version of template available

   for download &lt;a href="/misc/BT2004DeployWithNAntSample.zip"&gt;here&lt;/a&gt;.&lt;/font&gt;

&lt;/p&gt;

&lt;img width="0" height="0" src="http://www.traceofthought.net/aggbug.ashx?id=d0472142-ea34-4733-9eea-60a8f7d893be"&gt;</description>

      <link>http://www.traceofthought.net/PermaLink,guid,d0472142-ea34-4733-9eea-60a8f7d893be.aspx</link>

      <source url="http://www.traceofthought.net/">Trace of Thought (Scott Colestock)</source>

      <comments>http://www.traceofthought.net/CommentView,guid,d0472142-ea34-4733-9eea-60a8f7d893be.aspx</comments>

      <guid isPermaLink="False">http://www.traceofthought.net/PermaLink,guid,d0472142-ea34-4733-9eea-60a8f7d893be.aspx</guid>

      <pubDate>Tue, 07 Sep 2004 22:15:53 GMT</pubDate>

    </item>

    <item>

      <title>Welcome to the BizTalk Xml Tools' Web Log</title>

      <description>&lt;p&gt;Welcome to our blog. We're the development team within BizTalk currently responsible for Schema Editor, Mapper, Web Services Publishing Wizard, and Rules Composer.This is a way for us to communicate with the BizTalk community.&lt;/p&gt; &lt;p&gt;Stay Tuned.&lt;/p&gt;&lt;img src ="http://blogs.msdn.com/biztalkxmltools/aggbug/226385.aspx" width = "1" height = "1" /&gt;</description>

      <link>http://blogs.msdn.com/biztalkxmltools/archive/2004/09/07/226385.aspx</link>

      <source url="http://blogs.msdn.com/biztalkxmltools/">BizTalkXmlTools's WebLog</source>

      <comments>http://blogs.msdn.com/biztalkxmltools/archive/2004/09/07/226385.aspx#Feedback</comments>

      <guid isPermaLink="False">http://blogs.msdn.com/biztalkxmltools/archive/2004/09/07/226385.aspx</guid>

      <pubDate>Tue, 07 Sep 2004 13:55:00 GMT</pubDate>

    </item>

    <item>

      <title>BizTalk 2004 "Deploy with Nant" Template Revamp</title>

      <description>&lt;p&gt;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;It has been several months since I initially &lt;span style="FONT-WEIGHT: bold"&gt;&lt;a href="/PermaLink,guid,2e018262-cc86-4830-bdc6-871dfb1af51e.aspx"&gt;posted&lt;/a&gt; &lt;/span&gt;on

   the topic of using NAnt to coordinate the deployment of BizTalk 2004 solutions, with

   updates &lt;span style="FONT-WEIGHT: bold"&gt;&lt;a href="/PermaLink,guid,df02e4ab-590c-409c-8de9-8f54776de595.aspx"&gt;here&lt;/a&gt; &lt;/span&gt;and &lt;span style="FONT-WEIGHT: bold"&gt;&lt;a href="/PermaLink,guid,67b98ddc-95c3-48a0-bc0c-91adb95a381b.aspx"&gt;here&lt;/a&gt;&lt;/span&gt;.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;Since

   that time, I've been heads-down in a BizTalk project and have had a chance to refine

   the practice quite a bit.&lt;/font&gt;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;&lt;/font&gt;&amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;So, I took the opportunity to introduce quite a few improvements

   into the sample I had previously released - hopefully turning it into a "template"

   that can be used on your projects more easily.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;To

   that end, I've created a &lt;span style="FONT-WEIGHT: bold"&gt;&lt;a href="http://www.gotdotnet.com/workspaces/workspace.aspx?id=d66e1651-98e5-4ef4-9158-ac030a9b8a32"&gt;GotDotNet

   workspace&lt;/a&gt; &lt;/span&gt;where you can download the current version of the build template,

   and I invite any feedback/suggestions/participation.&lt;/font&gt;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;&lt;/font&gt;&amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;The major changes I've introduced can be categorized as follows:&lt;/font&gt;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;&lt;/font&gt;&amp;nbsp;

&lt;/p&gt;

&lt;ul style="MARGIN-TOP: 0in; MARGIN-BOTTOM: 0in; MARGIN-LEFT: 0.5in; DIRECTION: ltr; unicode-bidi: embed" type=disc&gt;

   &lt;li style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; mso-outline-level: 1"&gt;

      &lt;span style="FONT-FAMILY: Verdana"&gt;&lt;font color=#000000&gt;Split binding files: On a BizTalk

      project with multiple developers, I believe it is beneficial to split your binding

      files into content related to orchestrations vs. content relating to "everything else"

      (send ports, receive ports, etc.)&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;The

      new build template sample does just that.&lt;/font&gt;&lt;/span&gt;

   &lt;/li&gt;

&lt;/ul&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;&lt;/font&gt;&amp;nbsp;

&lt;/p&gt;

&lt;ul style="MARGIN-TOP: 0in; MARGIN-BOTTOM: 0in; MARGIN-LEFT: 0.5in; DIRECTION: ltr; unicode-bidi: embed" type=disc&gt;

   &lt;li style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; mso-outline-level: 1"&gt;

      &lt;span style="FONT-FAMILY: Verdana"&gt;&lt;font color=#000000&gt;Improved scripts: Many of the

      WMI-related scripts I relied on in the past were from BizTalk SDK samples.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;These

      were modified to get better/different error handling behavior.&lt;/font&gt;&lt;/span&gt;

   &lt;/li&gt;

&lt;/ul&gt;

&lt;p style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; mso-outline-level: 1"&gt;

   &lt;span style="FONT-FAMILY: Verdana"&gt;&lt;font color=#000000&gt;&lt;/font&gt;&lt;/span&gt;&amp;nbsp;

&lt;/p&gt;

&lt;ul style="MARGIN-TOP: 0in; MARGIN-BOTTOM: 0in; MARGIN-LEFT: 0.5in; DIRECTION: ltr; unicode-bidi: embed" type=disc&gt;

   &lt;li style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; mso-outline-level: 1"&gt;

      &lt;span style="FONT-FAMILY: Verdana"&gt;&lt;font color=#000000&gt;More generic handling of send

      ports, receive ports, receive locations, etc. in the script - though it still requires

      some&amp;nbsp;maintenance.&lt;/font&gt;&lt;/span&gt;

   &lt;/li&gt;

&lt;/ul&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;&lt;/font&gt;&amp;nbsp;

&lt;/p&gt;

&lt;ul style="MARGIN-TOP: 0in; MARGIN-BOTTOM: 0in; MARGIN-LEFT: 0.5in; DIRECTION: ltr; unicode-bidi: embed" type=disc&gt;

   &lt;li style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; mso-outline-level: 1"&gt;

      &lt;font color=#000000&gt;&lt;span style="FONT-FAMILY: Verdana"&gt;Better NAnt citizen: I'm still

      not a NAnt expert by any stretch, but thanks to &lt;/span&gt;&lt;span style="FONT-WEIGHT: bold; FONT-FAMILY: Verdana"&gt;&lt;a href="http://geekswithblogs.net/dmillard"&gt;Duncan

      Millard&lt;/a&gt;&lt;/span&gt;&lt;span style="FONT-FAMILY: Verdana"&gt; I realized that I had been remiss

      in applying quotes to a good deal of the text names I was using (i.e. &amp;amp;quot).&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;In

      addition, I started using built-in NAnt tasks for at least a few items where I had

      overlapped functionality, though not in cases where I needed slightly different behavior.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;Finally,

      the build file naming convention proposed by the build template is "BizTalkSample.sln.deploy.build"

      (rather than "BizTalkSample.sln.build") to avoid conflicting with a NAnt file that

      would actually be used to build the project (e.g. with Cruise Control), as opposed

      to deploying it. &lt;/span&gt;&lt;/font&gt;

   &lt;/li&gt;

&lt;/ul&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;&lt;/font&gt;&amp;nbsp;

&lt;/p&gt;

&lt;ul style="MARGIN-TOP: 0in; MARGIN-BOTTOM: 0in; MARGIN-LEFT: 0.5in; DIRECTION: ltr; unicode-bidi: embed" type=disc&gt;

   &lt;li style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; mso-outline-level: 1"&gt;

      &lt;font color=#000000&gt;&lt;span style="FONT-FAMILY: Verdana"&gt;Use of "Deploy with NAnt" in

      an &lt;/span&gt;&lt;span style="FONT-WEIGHT: bold; FONT-FAMILY: Verdana"&gt;MSI scenario&lt;/span&gt;&lt;span style="FONT-FAMILY: Verdana"&gt;:

      This is the biggest (and I believe most useful) change...Let me explain further.&lt;/span&gt;&lt;/font&gt;

   &lt;/li&gt;

&lt;/ul&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; COLOR: black; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   As you study the build script, you will notice that it now also tackles such tasks

   as deploying virtual directories and applying permissions to them, patching binding

   files to match &amp;#8220;local conditions&amp;#8221;, etc. The initial goal here is to ensure

   that in a team development scenario, the amount of &amp;#8220;out of band&amp;#8221; setup

   required for any given developer to establish their BizTalk 2004 project environment

   is minimal &amp;#8211; and that&amp;nbsp;the current&amp;nbsp;topology for the project is communicated

   efficiently (i.e. through the build file, as opposed to email or word-of-mouth.)

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; COLOR: black; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   After a development team has spent weeks or months with this build script, refining

   it to represent their exact situation and deployment needs, a question might arise: &lt;span style="FONT-STYLE: italic"&gt;Why

   not take this well-tested script and use it for production (or just non-development-machine)

   deployments as well?&lt;/span&gt;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; COLOR: black; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   To do this, it is helpful to agree that a two-phase deployment of BizTalk-related

   projects is both acceptable and useful. The first phase is an MSI-based installation

   that simply installs all of the BizTalk-related assets in a specific directory, but

   doesn&amp;#8217;t deploy them to the BizTalk server. The second phase occurs when the

   user goes to the Start-Programs-YourProjectName menu, and chooses &amp;#8220;Deploy YourProjectName&amp;#8221;.

   The user also has the option to un-deploy (leaving the assets still on the file system

   until the MSI is uninstalled) or redeploy (to support the case where a single file

   is &amp;#8220;patched&amp;#8221;.)&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; See a &lt;a href="/misc/menu.jpg"&gt;picture&lt;/a&gt;&lt;/span&gt; of

   the Start menu created by the build template's MSI file.

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; COLOR: black; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   The reason that two phases are useful is that if the deployment to BizTalk fails,

   we would like a complete log of the results (which in this sample occurs in the DeployResults

   directory) for analysis/diagnostics, and we would rather not have the MSI simply roll

   back. The same holds true of un-deployment.

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; COLOR: black; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   Dual-purposing the NAnt file you have been maintaining for &amp;#8220;real&amp;#8221; deployments

   can be summarized as follows:

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;ul&gt;

   &lt;li&gt;

      &lt;div style="MARGIN-TOP: 0px; FONT-SIZE: 12pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; mso-outline-level: 2"&gt;&lt;span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana"&gt;Use

         the build template's approach (see BizTalkSample.sln.deploy.build in the download)

         for the &amp;#8220;server.deploy&amp;#8221; and &amp;#8220;server.undeploy&amp;#8221; targets, which

         make the build file able to work with &amp;#8220;co-located&amp;#8221; binaries in addition

         to the standard developer tree.&lt;/span&gt;

      &lt;/div&gt;

   &lt;li&gt;

      &lt;div style="MARGIN-TOP: 0px; FONT-SIZE: 12pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; mso-outline-level: 2"&gt;&lt;span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana"&gt;Create

         a Visual Studio Setup project that deploys your BizTalk assemblies according to the

         pattern shown in the BizTalkSample.Setup project. Notice that this setup project includes

         the NAnt build file, the &amp;#8220;DeployTools&amp;#8221; directory (with our scripts), as

         well as a subset of NAnt in a subdirectory of our installation (so that we don&amp;#8217;t

         rely on NAnt being present on the target server.)&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;It

         also includes a few convenience batch files referenced by our Start menu entries for

         invoking NAnt with specific targets.&lt;/span&gt;

      &lt;/div&gt;

   &lt;/li&gt;

&lt;/ul&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;The BizTalkSample.Setup project in the build file can be built,

   installed, and deployed to try this out.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;(You

   will want to make sure you haven't already deployed in "developer" mode, because the

   "Deploy BizTalk Deployment Sample" passes a flag to the NAnt script that will &lt;span style="FONT-STYLE: italic"&gt;skip&lt;/span&gt; the

   undeploy phase in order to speed up "clean" installations.)&amp;nbsp;&amp;nbsp;Note that as

   your deployment grows more sophisticated - multiple hosts, servers, etc.&amp;nbsp;- you

   will find the NAnt script requires additional properties to govern these variations

   between server deployments and developer-desktop deployments.

&lt;/p&gt;

&gt; 

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;&lt;/font&gt;&amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;The build template sample also discusses the use of NUnit as a

   post-deployment verification process.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;See

   the &lt;span style="FONT-WEIGHT: bold"&gt;&lt;a href="http://www.gotdotnet.com/workspaces/releases/viewuploads.aspx?id=d66e1651-98e5-4ef4-9158-ac030a9b8a32"&gt;documentation&lt;/a&gt; &lt;/span&gt;in

   the sample for a full discussion --&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;basically

   all we are doing is making sure our MSI includes a subset of our unit tests, NUnit,

   and appropriate test files.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;This is then

   wired up to the "Verify Deployment" Start menu option.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;This

   can be an extremely effective means of ensuring your operations team has a means of

   testing the system interactively (not to replace standard automated heartbeat tests

   you might have&amp;#8230;)&lt;/font&gt;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;&lt;/font&gt;&amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;&lt;span style="FONT-WEIGHT: bold"&gt;&lt;a href="http://www.peterprovost.org/archive/2004/08/18/1802.aspx"&gt;Peter

   Provost&lt;/a&gt; &lt;/span&gt;proposed a great generic approach to building BizTalk NAnt files

   a couple of weeks ago - and I shamelessly stole his approach to reverse the "orchestration

   ordering" property (very slick!)&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;If you

   do not wish to pursue the MSI option just discussed, and you do not wish to integrate

   the "out of band" setup actions discussed above (i.e. virtual directory creation,

   etc.), you might prefer his approach or you might want to push the build template

   sample provided here in that direction (i.e. more property driven.)&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;However,

   I believe tackling the kinds of concerns that we do here will generally mean that

   a real-world project will no longer have a generic-looking NAnt script.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/font&gt;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;&lt;/font&gt;&amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &lt;font color=#000000&gt;Again, you can download the build template sample &lt;a href="http://www.gotdotnet.com/workspaces/workspace.aspx?id=d66e1651-98e5-4ef4-9158-ac030a9b8a32"&gt;here&lt;/a&gt;.&amp;nbsp;

   Enjoy, and I hope you find it useful.&lt;/font&gt;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;img width="0" height="0" src="http://www.traceofthought.net/aggbug.ashx?id=09ad4181-dde2-4906-884b-d023f80fc800"&gt;</description>

      <link>http://www.traceofthought.net/PermaLink,guid,09ad4181-dde2-4906-884b-d023f80fc800.aspx</link>

      <source url="http://www.traceofthought.net/">Trace of Thought (Scott Colestock)</source>

      <comments>http://www.traceofthought.net/CommentView,guid,09ad4181-dde2-4906-884b-d023f80fc800.aspx</comments>

      <guid isPermaLink="False">http://www.traceofthought.net/PermaLink,guid,09ad4181-dde2-4906-884b-d023f80fc800.aspx</guid>

      <pubDate>Sun, 05 Sep 2004 05:41:21 GMT</pubDate>

    </item>

    <item>

      <title>MSMQT Observations...</title>

      <description>&lt;p&gt;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   A lot has been said regarding the MSMQT adapter for BizTalk 2004 already, but below

   are a few recent observations that may be of help to you.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   When people ask me what MSMQT is, my short answer goes something like this: "MSMQT

   is the name of the BizTalk 2004 adapter that &lt;span style="FONT-STYLE: italic"&gt;implements

   the MSMQ network protocol directly within BizTalk.&lt;/span&gt;&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;It

   allows BizTalk 2004 to send/receive MSMQ messages directly, and move messages to/from

   the MessageBox very quickly - without external (DTC) transaction coordination.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;Only

   private queues are supported for receives."

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   Using the MSMQT adapter you can:

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;ul style="MARGIN-TOP: 0in; MARGIN-BOTTOM: 0in; MARGIN-LEFT: 0.5in; DIRECTION: ltr; unicode-bidi: embed" type=disc&gt;

   &lt;li style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; mso-outline-level: 1"&gt;

      &lt;span style="FONT-FAMILY: Verdana"&gt;Use Send Ports to send to public or private queues

      on remote machines - but the &lt;/span&gt;&lt;span style="FONT-STYLE: italic; FONT-FAMILY: Verdana"&gt;queues

      must be transactional.&lt;/span&gt;

   &lt;/li&gt;

&lt;/ul&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-STYLE: italic; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;ul style="MARGIN-TOP: 0in; MARGIN-BOTTOM: 0in; MARGIN-LEFT: 0.5in; DIRECTION: ltr; unicode-bidi: embed" type=disc&gt;

   &lt;li style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; mso-outline-level: 1"&gt;

      &lt;span style="FONT-FAMILY: Verdana"&gt;Use Send Ports to send to local queues, which will

      be &lt;/span&gt;&lt;span style="FONT-STYLE: italic; FONT-FAMILY: Verdana"&gt;private &lt;/span&gt;&lt;span style="FONT-FAMILY: Verdana"&gt;since

      that is all MSMQT supports.&lt;/span&gt;

   &lt;/li&gt;

&lt;/ul&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;ul style="MARGIN-TOP: 0in; MARGIN-BOTTOM: 0in; MARGIN-LEFT: 0.5in; DIRECTION: ltr; unicode-bidi: embed" type=disc&gt;

   &lt;li style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; mso-outline-level: 1"&gt;

      &lt;span style="FONT-FAMILY: Verdana"&gt;Use Receive Locations to receive from locally defined

      queues, which will be &lt;/span&gt;&lt;span style="FONT-STYLE: italic; FONT-FAMILY: Verdana"&gt;private &lt;/span&gt;&lt;span style="FONT-FAMILY: Verdana"&gt;since

      that is all MSMQT supports.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;These queues

      can be either transactional or non-transactional.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;You

      cannot monitor remote queues (i.e. receive locations can't reference remote queues.)&lt;/span&gt;

   &lt;/li&gt;

&lt;/ul&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   You cannot using the System.Messaging MSMQ APIs/COM MSMQ APIs/MSMQ C Libraries or

   the MSMQ MMC console on a BizTalk 2004 machine that is running the MSMQT adapter!&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;This

   is because these all rely on the native &lt;span style="FONT-STYLE: italic"&gt;MSMQ Service&lt;/span&gt; running.

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   You &lt;span style="FONT-STYLE: italic"&gt;can &lt;/span&gt;use the aforementioned APIs (though

   not the MMC console) from remote machines (that are not running the MSMQT adapter)

   to put messages in MSMQT-defined queues.

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   To test MSMQT queues on the BizTalk 2004 server where they are defined, you can:

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;ol style="MARGIN-TOP: 0in; MARGIN-BOTTOM: 0in; MARGIN-LEFT: 0.5in; DIRECTION: ltr; unicode-bidi: embed" type=1&gt;

   &lt;li style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; FONT-FAMILY: Verdana; mso-outline-level: 1" value=1&gt;

      Create a Receive Port and a File Receive Location that will monitor a particular directory...&lt;/li&gt;

   &lt;li style="MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-BOTTOM: 0px; VERTICAL-ALIGN: middle; FONT-FAMILY: Verdana; mso-outline-level: 1" value=2&gt;

      Create a static one-way Send Port that specifies MSMQT &amp;amp; the queue you want to

      test as the destination.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;In the "Filters"

      portion of the Send Port configuration, define BTS.ReceivePortName = ReceivePortNameFromStep1&lt;/li&gt;

&lt;/ol&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   Now, when we you drop a file on your directory, it will be routed to your queue.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;The

   receive location could also use HTTP posts, in which case the WFETCH tool from the

   IIS Resource Kit (or a similar tool) will let you easily get test messages to the

   queue.

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   Note: If you have existing applications that used to send to public MSMQ queues, but

   will now be sending to MSMQT queues, the most common problem is that they are referencing

   those queues via the PathName property, rather than the FormatName property (with

   'DIRECT=OS:machine\private$\qname' syntax.)&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;This

   is only a problem for users of the COM/C-Library APIs - the System.Messaging.MessageQueue

   class actually allows format names to be used with the Path property.

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   &amp;nbsp;

&lt;/p&gt;

&lt;p style="FONT-SIZE: 10pt; MARGIN: 0in; FONT-FAMILY: Verdana; mso-outline-level: 1"&gt;

   See&amp;nbsp;this &lt;a href="http://support.microsoft.com/default.aspx?scid=%2Fservicedesks%2Fwebcasts%2Fen%2Ftranscripts%2Fwct030204.asp"&gt;Microsoft

   Support discussion&lt;/a&gt; for lots of&amp;nbsp;additional insight into MSMQT.

&lt;/p&gt;

&lt;img width="0" height="0" src="http://www.traceofthought.net/aggbug.ashx?id=43449b0b-663b-4f3d-9a47-e684fd5347d4"&gt;</description>

      <link>http://www.traceofthought.net/PermaLink,guid,43449b0b-663b-4f3d-9a47-e684fd5347d4.aspx</link>

      <source url="http://www.traceofthought.net/">Trace of Thought (Scott Colestock)</source>

      <comments>http://www.traceofthought.net/CommentView,guid,43449b0b-663b-4f3d-9a47-e684fd5347d4.aspx</comments>

      <guid isPermaLink="False">http://www.traceofthought.net/PermaLink,guid,43449b0b-663b-4f3d-9a47-e684fd5347d4.aspx</guid>

      <pubDate>Wed, 25 Aug 2004 23:31:20 GMT</pubDate>

    </item>

    <item>

      <title>BizTalk Server 2004 - Native Parsing Error Gotcha!</title>

      <description>&lt;P&gt;&lt;FONT face=Verdana size=1&gt;This has definitely been my week for BizTalk surprises! Having successfully deployed several flat-file to XML&amp;nbsp;maps with very little trouble, I never expected to see &amp;#8220;&lt;FONT color=#ff0000&gt;Native parsing error: The path is not of a legal form&lt;/FONT&gt;&amp;#8221; during routine testing of a new map. This error had me stumped for several hours, since my flat-file schema tested just fine against the same instance document I was using to test my map. Being a very stubborn developer, I assumed my map was at fault and&amp;nbsp;proceeded to test each and every link to see where the error occurred. After several hours with no luck, I even went so far as to create a new map with no links between the inbound and outbound schemas but the same error occurred.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;Then I did what I should have done much much earlier. I went to the MS support&amp;nbsp;site and searched for any BizTalk Server KB articles containing&amp;nbsp;the text &amp;#8220;native parsing error&amp;#8221;. The KB article &lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;837857&amp;amp;Product=bizt2002"&gt;837857&lt;/A&gt; was exactly what I was looking for, although the explanation behind this error was pretty slim. According to this&amp;nbsp;article, the error occurs when your map refers to a schema in an external assembly and when the &lt;STRONG&gt;Input&lt;/STRONG&gt; or &lt;STRONG&gt;Output&lt;/STRONG&gt; settings for the map test are set to &lt;STRONG&gt;Native&lt;/STRONG&gt;. Actually, this error only occurs if your flat-file schema is in an external assembly.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;The work-around is shown below:&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana color=#006400 size=1&gt;1. Temporarily move the schema to the same project as the map that you want to test.&lt;BR&gt;2. Configure the map to use the schema now in your project.&lt;BR&gt;3. Test the map using the settings you want.&lt;BR&gt;4. Move the schema back to the original location.&lt;BR&gt;5. Set the BizTalk Mapper back to use the original&amp;nbsp;location of the schema.&lt;BR&gt;6. Make sure everything is back to it's original state before compiling your project!&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;The moral of this post is clear. &lt;STRONG&gt;CHECK THE KB BEFORE&amp;nbsp;SPENDING HOURS DEBUGGING!&lt;/STRONG&gt; &lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;I hope MS fixes this bug very soon (can you say hot-fix?).&lt;/FONT&gt;&lt;/P&gt;&lt;HR NOSHADE SIZE="1"&gt;This Blog Hosted On: http://www.DotNetJunkies.com/&lt;img src ="http://dotnetjunkies.com/WebLog/jlynch/aggbug/23127.aspx" width = "1" height = "1" /&gt;</description>

      <link>http://dotnetjunkies.com/WebLog/jlynch/archive/2004/08/24/23127.aspx</link>

      <source url="http://dotnetjunkies.com/WebLog/jlynch/">A BizTalk Enthusiast</source>

      <comments>http://dotnetjunkies.com/WebLog/jlynch/archive/2004/08/24/23127.aspx#Feedback</comments>

      <guid isPermaLink="False">http://dotnetjunkies.com/WebLog/jlynch/archive/2004/08/24/23127.aspx</guid>

      <pubDate>Tue, 24 Aug 2004 17:45:00 GMT</pubDate>

    </item>

    <item>

      <title>BizTalk Server 2004 - Windows XP Service Pack 2 Gotcha!</title>

      <description>&lt;P&gt;&lt;FONT face=Verdana size=1&gt;I installed WinXP SP2 on my main development workstation this weekend after reviewing much of the support documentation and&amp;nbsp;a recent BTS2004 KB article (&lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;841893"&gt;841893&lt;/A&gt;). The install of SP2 went fine and after making the registry changes outlined in the article, the SSO service started again and I went back to work revising my current BTS2004 solution for deployment on Monday morning.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;I usually use the BizTalk Explorer to "manage" both my local development instance of BTS2004 as well as my production servers (BTS2004 and SQL2000). Due to the nature of my revisions, I needed to completely undeploy and redeploy my solution on the production servers. Having thoroughly tested&amp;nbsp;the redeployment on my development notebook during the weekend, I was surprised to find that I could not delete any receive ports, send ports or send port groups on my production servers using the BizTalk Explorer on my development notebook (See the error message below). Since I had several inbound and outbound maps and custom pipelines deployed in my solution, the only way to undeploy the assemblies is to first delete the ports and port groups referencing these and without the BizTalk Explorer, I was stuck. I then disabled my receive port and watched the inbound messages pile up.&lt;BR&gt;&lt;BR&gt;&lt;IMG src="/WebLog/images/dotnetjunkies_com/jlynch/1403/o_error3.gif"&gt;&lt;BR&gt;&lt;STRONG&gt;Figure 1: What an Informative Error Message (Not)&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;I opened a support case using my &lt;A href="http://msdn.microsoft.com/subscriptions/"&gt;MSDN Universal&lt;/A&gt; subscription and the support technician, Vipul Goyal [MSFT] emailed me back within 30 minutes! A few minutes later we were on the phone discussing the problem and Vipul offered several suggestions to try. When none of these worked, he pointed me to the WMI scripts in the SDK that would allow me (with a little modification I'll discuss in a future post) to delete my ports and port groups&amp;nbsp;and redeploy my solution. While I was doing this, he contacted the BTS product team, the SP2 QFE team&amp;nbsp;and confirmed the issue. Using the WMI scripts and the BizTalk Deployment Wizard, I was able to redeploy my revised solution and restarted my receive ports. Back up and running in under four hours! Late this afternoon, I received the email from Vipul with the "fix"&amp;nbsp;(which turned out to be a blinding flash of the obvious - exclude MSDTC from the firewall) which works great.&lt;BR&gt;&lt;BR&gt;&lt;IMG src="/WebLog/images/dotnetjunkies_com/jlynch/1403/o_firewall2.gif"&gt;&lt;BR&gt;&lt;STRONG&gt;Figure 2: Firewall Exceptions&lt;/STRONG&gt;&lt;BR&gt;&lt;BR&gt;&lt;IMG src="/WebLog/images/dotnetjunkies_com/jlynch/1403/o_firewall3.gif"&gt;&lt;BR&gt;&lt;STRONG&gt;Figure 3: Adding the MSDTC exception&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;/P&gt;&lt;FONT face=Verdana color=#ff0000 size=2&gt;&lt;EM&gt;&lt;STRONG&gt;Special thanks to Vipul Goyal [MSFT] for your help, support and quick thinking!&lt;/STRONG&gt;&lt;/EM&gt;&lt;/FONT&gt;&lt;HR NOSHADE SIZE="1"&gt;This Blog Hosted On: http://www.DotNetJunkies.com/&lt;img src ="http://dotnetjunkies.com/WebLog/jlynch/aggbug/23022.aspx" width = "1" height = "1" /&gt;</description>

      <link>http://dotnetjunkies.com/WebLog/jlynch/archive/2004/08/23/23022.aspx</link>

      <source url="http://dotnetjunkies.com/WebLog/jlynch/">A BizTalk Enthusiast</source>

      <comments>http://dotnetjunkies.com/WebLog/jlynch/archive/2004/08/23/23022.aspx#Feedback</comments>

      <guid isPermaLink="False">http://dotnetjunkies.com/WebLog/jlynch/archive/2004/08/23/23022.aspx</guid>

      <pubDate>Mon, 23 Aug 2004 21:05:00 GMT</pubDate>

    </item>

    <item>

      <title>BizTalk Server 2004 - A Simple Deployment Scenario!</title>

      <description>&lt;P&gt;&lt;FONT face=Verdana size=1&gt;OK, we've built our&amp;nbsp;little BizTalk solution according to the latest &amp;#8220;best practices&amp;#8221;, putting standard schemas in one project,&amp;nbsp;solution related schemas and maps in another project and our custom pipelines in a third project. We've build these in &amp;#8220;Development&amp;#8221; configuration and tested every possible combination of failures including parsing errors, mapping errors, transmission errors and even (old reliable) human error! We've configured&amp;nbsp;our receive and send ports and HAT for maximum safety (no lost documents - or else!). We've reviewed possible security threats and created backups of backups of backups. Finally, we've exported our assembly binding to a file after selecting &amp;#8220;&lt;FONT color=#006400&gt;Export items not associated with any assembly:&amp;#8221; &lt;/FONT&gt;(this is important since we are not using an Orchestration in our solution)&amp;nbsp;and made the required modifications for our target server.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;So... we change our configuration from &amp;#8220;Development&amp;#8220; to &amp;#8220;Deployment&amp;#8220; and build each project &lt;STRONG&gt;IN REVERSE ORDER OF DEPENDENCY&lt;/STRONG&gt;, changing our References to point to the &amp;#8220;Deployment&amp;#8220; version of each dependent assembly as shown in Figure 1.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;&lt;IMG src="/WebLog/images/dotnetjunkies_com/jlynch/1403/o_projects.gif"&gt;&lt;BR&gt;&lt;STRONG&gt;Figure 1: Assembly Dependencies&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;Now we're ready to deploy our simple BizTalk solution in a simple manner!&lt;BR&gt;&lt;BR&gt;1. We copy our assemblies to our target server, placing them in a folder such as C:\BizTalk Assemblies.&lt;BR&gt;2. We deploy each assembly using the BizTalk Deployment Wizard &lt;STRONG&gt;&lt;A href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/deploying/htm/ebiz_depl_assemblies_eaqt.asp"&gt;IN REVERSE ORDER OF DEPENDENCY&lt;/A&gt;&lt;/STRONG&gt;.&lt;BR&gt;3. We import our BizTalk assembly binding&amp;nbsp;&lt;STRONG&gt;&lt;A href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/deploying/htm/ebiz_asdepl_concepts_hqzj.asp"&gt;FOR OUR DEPLOYED CONFIGURATION&lt;/A&gt;&lt;/STRONG&gt;.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;Now everything should be deployed to the target server and be registered in both the configuration database and the global assembly cache as shown in Figure 2.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;&lt;IMG src="/WebLog/images/dotnetjunkies_com/jlynch/1403/o_deployment.gif"&gt;&lt;BR&gt;&lt;STRONG&gt;Figure 2: Our Deployed Solution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;4. Our final step is to &amp;#8220;enlist&amp;#8221; and &amp;#8220;start&amp;#8221; our send ports and send port groups and wait for the magic to happen! &lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=1&gt;Not too bad considering the fact that the BTS2004 documentation&amp;nbsp;has over 125 pages covering &amp;#8220;deployment&amp;#8221;. If you're like me, this section of the help file was one of the most daunting to understand. Any set of instructions that requires a &lt;A href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/deploying/htm/ebiz_asdepl_howto_nbbr.asp"&gt;flow-chart like this&lt;/A&gt; is way too complicated. Trust me! It's really not too bad if you keep things simple.&lt;/FONT&gt;&lt;/P&gt;&lt;HR NOSHADE SIZE="1"&gt;This Blog Hosted On: http://www.DotNetJunkies.com/&lt;img src ="http://dotnetjunkies.com/WebLog/jlynch/aggbug/21672.aspx" width = "1" height = "1" /&gt;</description>

      <link>http://dotnetjunkies.com/WebLog/jlynch/archive/2004/08/10/21672.aspx</link>

      <source url="http://dotnetjunkies.com/WebLog/jlynch/">A BizTalk Enthusiast</source>

      <comments>http://dotnetjunkies.com/WebLog/jlynch/archive/2004/08/10/21672.aspx#Feedback</comments>

      <guid isPermaLink="False">http://dotnetjunkies.com/WebLog/jlynch/archive/2004/08/10/21672.aspx</guid>

      <pubDate>Tue, 10 Aug 2004 19:49:00 GMT</pubDate>

    </item>

    <item>

      <title>BizTalk Server 2004: FTP guaranteed delivery</title>

      <description>&lt;P&gt;&lt;FONT face=Verdana size=2&gt;The BizTalk Server 2004 FTP adapter offers a 'guaranteed delivery' feature, the details of which are not documented by Microsoft.&amp;nbsp; The mechanism is very straightforward, however, and involves the use of a temporary folder.&amp;nbsp;&amp;nbsp; Files are staged by BizTalk in this folder before being moved to the destination folder.&amp;nbsp;&amp;nbsp; BizTalk supports this for both Send and Receive handlers.&amp;nbsp; To use this feature, simply set the "Temporary Folder" property of the FTP adapter.&amp;nbsp;&amp;nbsp; For Send ports, this will be the name of an FTP folder on the server, rather than a local folder. &lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=2&gt;The main advantage of using this feature is that retries can be performed in the event of a transport failure, with multiple copies of the same file being sent to the temporary folder.&amp;nbsp;&amp;nbsp; However, at most, only one copy of the file will ever be moved to the destination folder or receive location.&amp;nbsp;&amp;nbsp; The use of staging eliminates the possibility (in theory) of the FTP server (Send port) or BizTalk (Receive port) receiving multiple copies of the same file.&amp;nbsp;&amp;nbsp; Another advantage is that you can ensure that a file is received in entirety, or not at all.&amp;nbsp;&amp;nbsp; FTP allows files to be partially transferred, and supports transfer recovery where a partially completed transfer can be re-started from the point of failure (FTP regets and reputs).&amp;nbsp;&amp;nbsp; While this is a great feature in some scenarios, it is potentially a killer in BizTalk, because it can lead to BizTalk believing it has received or sent a file, when in fact the file has only been partially transferred.&amp;nbsp;&amp;nbsp; The use of a temporary staging folder allows a file to be fully transported before being transferred to its destination folder or receive location.&amp;nbsp;&amp;nbsp; This is particularly useful when transporting large files or transporting files over un-reliable networks.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=2&gt;You do need to be very careful when using the feature on a receive port.&amp;nbsp; You configure the temporary folder at the host level via the BTS Administrative console.&amp;nbsp;&amp;nbsp; If you have multiple servers in your BizTalk group, and run multiple instances of you host across those boxes, each instance will point to the same temporary folder.&amp;nbsp; In this case, things go badly wrong.&amp;nbsp;&amp;nbsp; Unlike the File adapter, instances of the native FTP adapter do not lock or rename files in order to prevent other instances from processing the same input.&amp;nbsp;&amp;nbsp; Hence, bad things happen.&amp;nbsp;&amp;nbsp; It is possible to have multiple instances of the same message delivered to the MessageBox, even though you are using the 'guaranteed deliver' feature.&amp;nbsp; In addition, when one instance of the adapter moves a file from the temporary folder, a second instance then fails when it tries to do the same thing, and cannot find the file.&amp;nbsp;&amp;nbsp; Always isolate your FTP adapter in a separate host, and always run just one instance for a receive handler.&amp;nbsp;&amp;nbsp; One idea might be to assign your FTP-receiving host to multiple servers, but only enable one of the host instances.&amp;nbsp;&amp;nbsp; You could then use WMI to automate a fail-over to another instance in the event of a failure.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=2&gt;Here is an extract from the FTP log showing exactly what commands the Send adapter sends to an external FTP server on a successful transfer.&amp;nbsp; In this case we are FTPing a file called {0d41d46a-f73a-4675-b7d2-51ffea0983e3}.xml to &lt;/FONT&gt;&lt;A href="ftp://ftpServer:21/Import"&gt;&lt;FONT face=Verdana size=2&gt;ftp://ftpServer:21/Import&lt;/FONT&gt;&lt;/A&gt;&lt;FONT face=Verdana size=2&gt;.&amp;nbsp;&amp;nbsp; Note how a temporary copy of the file is staged in the temporary folder (&lt;/FONT&gt;&lt;A href="ftp://ftpServer:21/ImportStaging"&gt;&lt;FONT face=Verdana size=2&gt;ftp://ftpServer:21/ImportStaging&lt;/FONT&gt;&lt;/A&gt;&lt;FONT face=Verdana size=2&gt;) and then moved to the destination folder once BizTalk knows it has been staged.&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=2&gt;USER developer1&lt;BR&gt;PASS&lt;BR&gt;CWD ImportStaging&lt;BR&gt;created /ImportStaging/{01d8b961-d37d-9513-f09d49454be7}&lt;BR&gt;RNFR {01d8b961-d37d-9513-f09d49454be7}&lt;BR&gt;RNTO /Import/{0d41d46a-f73a-4675-b7d2-51ffea0983e3}.xml&lt;BR&gt;QUIT&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana size=2&gt;&amp;nbsp;In English, this translates as follows:&lt;/FONT&gt;&lt;/P&gt;

&lt;UL&gt;

&lt;LI&gt;&lt;FONT face=Verdana size=2&gt;Establish an authenticated connection to the FTP server by sending a username and password &lt;/FONT&gt;

&lt;LI&gt;&lt;FONT face=Verdana size=2&gt;Request the server to change its working directory to the staging (transfer) directory&lt;/FONT&gt; 

&lt;LI&gt;&lt;FONT face=Verdana size=2&gt;FTP the file to the working directory under a temporary file name &lt;/FONT&gt;

&lt;LI&gt;&lt;FONT face=Verdana size=2&gt;When a response is received indicating that the file has been created on the server, request the server to move the transfer file to the destination folder and rename it &lt;/FONT&gt;

&lt;LI&gt;&lt;FONT face=Verdana size=2&gt;Terminate the connection &lt;/FONT&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;img src ="http://geekswithblogs.net/cyoung/aggbug/9524.aspx" width = "1" height = "1" /&gt;</description>

      <link>http://geekswithblogs.net/cyoung/archive/2004/08/10/9524.aspx</link>

      <source url="http://geekswithblogs.net/cyoung/">Charles Young</source>

      <comments>http://geekswithblogs.net/cyoung/archive/2004/08/10/9524.aspx#Feedback</comments>

      <guid isPermaLink="False">http://geekswithblogs.net/cyoung/archive/2004/08/10/9524.aspx</guid>

      <pubDate>Tue, 10 Aug 2004 13:03:00 GMT</pubDate>

    </item>

    <item>

      <title>What's wrong with the MSDN Library on CD?</title>

      <description>&lt;P&gt;I have always been&amp;nbsp;a great fan of the offline MSDN Library. I always have a very recent version installed on my PC and promoted it to every developer. &lt;/P&gt;

&lt;P&gt;But I've been disappointed by the July 2004 edition twice now. It both lacks the complete BizTalk 2004 documentation (a version is available since march, a decent one since April 2) and the complete Reporting Services documentation (the tool is around at least as long as BizTalk). It means that we have to wait at least half a year between product launch and offline MSDN documentation. I find that unbelieveable.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;img src ="http://sphear.demon.nl/weblogs/carlo/aggbug/1233.aspx" width = "1" height = "1" /&gt;</description>

      <link>http://sphear.demon.nl/weblogs/carlo/archive/2004/08/09/1233.aspx</link>

      <source url="http://sphear.demon.nl/weblogs/carlo/">CaPo's Integration adventures</source>

      <comments>http://sphear.demon.nl/weblogs/carlo/archive/2004/08/09/1233.aspx#Feedback</comments>

      <guid isPermaLink="False">http://sphear.demon.nl/weblogs/carlo/archive/2004/08/09/1233.aspx</guid>

      <pubDate>Mon, 09 Aug 2004 22:25:00 GMT</pubDate>

    </item>

    <item>

      <title>Visio stencil to describe Integration patterns</title>

      <description>&lt;P&gt;I found &lt;A href="http://www.enterpriseintegrationpatterns.com/download/EIP%20Visio%20Stencil.zip"&gt;this&lt;/A&gt;&amp;nbsp;visio stencil from the EAI Bible site &lt;A href="http://www.enterpriseintegrationpatterns.com"&gt;http://www.enterpriseintegrationpatterns.com&lt;/A&gt; great to help describe the problems I'm trying to solve in my current project. It contains 'standard' icons to represent all the patterns, like request/response, message filtering, content based routing, found in the book and on the website. &lt;/P&gt;

&lt;P&gt;I'm still looking for a visio stencil to describe the standard elements of a BizTalk 2004 solution, like Ports, Filters, Orchestrations, Messagebox, etc. Anyone aware of such a stencil?&lt;/P&gt;&lt;img src ="http://sphear.demon.nl/weblogs/carlo/aggbug/1222.aspx" width = "1" height = "1" /&gt;</description>

      <link>http://sphear.demon.nl/weblogs/carlo/archive/2004/08/05/1222.aspx</link>

      <source url="http://sphear.demon.nl/weblogs/carlo/">CaPo's Integration adventures</source>

      <comments>http://sphear.demon.nl/weblogs/carlo/archive/2004/08/05/1222.aspx#Feedback</comments>

      <guid isPermaLink="False">http://sphear.demon.nl/weblogs/carlo/archive/2004/08/05/1222.aspx</guid>

      <pubDate>Thu, 05 Aug 2004 17:06:00 GMT</pubDate>

    </item>

    <item>

      <title>Bug in CustomPartyResolution SDK Pipeline Sample...</title>

      <description>&lt;P&gt;&lt;A href="http://www.u-g-h.com/"&gt;&lt;FONT face=Verdana color=#0000ff size=2&gt;&lt;STRONG&gt;Owen&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/A&gt;&lt;FONT face=Verdana color=#0000ff size=2&gt; found a bug today in the custom party resolution SDK pipeline component located in @ $:\Program Files\Microsoft BizTalk Server 2004\SDK\Samples\Pipelines\CustomPartyResolution.&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana color=#0000ff size=2&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana&gt;&lt;FONT color=#0000ff size=2&gt;The bug is in the Read() method in the PartyResolutionStream class:&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;

&lt;P&gt;&lt;FONT face=Verdana color=#0000ff size=2&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Courier New'"&gt;public override int&lt;/SPAN&gt;&lt;SPAN