Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Writing a custom MSMQ connector

5 views
Skip to first unread message

Sam

unread,
Oct 20, 2008, 3:55:03 PM10/20/08
to
1. Is there any documentation on writing a MSMQ connector? Other than these
which aren't very useful:

http://msdn.microsoft.com/en-us/library/ms706915(VS.85).aspx
http://technet.microsoft.com/en-us/library/cc757108.aspx
http://msdn.microsoft.com/en-us/library/ms711472(VS.85).aspx

A code stub would be nice to get me started. I have a ton of network
programming experience on other platforms, but I always find it painful to
write plugin components for Microsoft products. I'm leaning toward writing
my own system to deal with this instead of using MSMQ foreign queues.

2. Can a connector be written in the .NET framework or am I going to have to
write this thing in C++? I'd hate to have to write it in C++ because it's
slower to write the code and it also means that I'd be the one supporting it
FOREEVER...

3. Unrelated, but can you guys delete the spam messages on these boards?

Thanks

Sam

unread,
Oct 21, 2008, 5:25:01 PM10/21/08
to
Nevermind. I figured it out on my own by putting about 10 different sources
together. The answers:

1) Probably not, but if you google enough and are like me, you can put about
15 different sources together to figure out how to do it.

2) Yes, it can be written in .NET. The things that weren't obvious were:
a) the format name for the queue will be something like:
"FormatName:CONNECTOR=ae34c88f-6110-41b9-a4a5-3dcc82273745", not
"FormatName:CONNECTOR=hostname\guid".
b) the connector queue is transient and will disappear on you if nothing is
in it and it hasn't been used for a while.
c) the connector queue MUST be opened on the server that it's on and you
can't change the access rights on the queue.

John Breakwell (MSFT)

unread,
Oct 23, 2008, 5:34:57 AM10/23/08
to
I'll go and find someone to hassle over this.

Cheers
John Breakwell (MSFT)

"Sam" <S...@discussions.microsoft.com> wrote in message
news:881D7987-8C6B-4F6B...@microsoft.com...

0 new messages