<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Getting a Clustered MSMQ Queue Length with .Net and COM</title>
	<atom:link href="http://jbablog.com/2008/06/getting-a-clustered-msmq-queue-length-with-net-and-com/feed/" rel="self" type="application/rss+xml" />
	<link>http://jbablog.com/2008/06/getting-a-clustered-msmq-queue-length-with-net-and-com/</link>
	<description>the personal blog of John BouAntoun</description>
	<lastBuildDate>Thu, 24 Nov 2011 16:24:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: John Breakwell</title>
		<link>http://jbablog.com/2008/06/getting-a-clustered-msmq-queue-length-with-net-and-com/comment-page-1/#comment-94</link>
		<dc:creator>John Breakwell</dc:creator>
		<pubDate>Wed, 18 Jun 2008 14:51:23 +0000</pubDate>
		<guid isPermaLink="false">http://jbablog.com/?p=45#comment-94</guid>
		<description>Getting FormatNames right is one of the main stumbling blocks in MSAQ programming. If there is one thing I could change in the product it would be to scrap the PathName/Formatname mess and create something simpler. 
I do, though, have the advantage of hindsight here - the design goals for MSMQ in the early 90s would not be the same now as customer environments and needs have changed/evolved so much - so I can cut out the parts that I know don&#039;t work or get used. 

Here&#039;s a good resource for FormatName examples.
MSMQQueueInfo.FormatName
http://msdn.microsoft.com/en-us/library/ms705703(VS.85).aspx

Cheers
John</description>
		<content:encoded><![CDATA[<p>Getting FormatNames right is one of the main stumbling blocks in MSAQ programming. If there is one thing I could change in the product it would be to scrap the PathName/Formatname mess and create something simpler.<br />
I do, though, have the advantage of hindsight here &#8211; the design goals for MSMQ in the early 90s would not be the same now as customer environments and needs have changed/evolved so much &#8211; so I can cut out the parts that I know don&#8217;t work or get used. </p>
<p>Here&#8217;s a good resource for FormatName examples.<br />
MSMQQueueInfo.FormatName<br />
<a href="http://msdn.microsoft.com/en-us/library/ms705703(VS.85).aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms705703(VS.85).aspx</a></p>
<p>Cheers<br />
John</p>
]]></content:encoded>
	</item>
</channel>
</rss>

