Message Queue!

[DBC User]

Hi All,

I am going to develop two application which will talk to each other
using MSMQ. I have couple of questions

1. Do we need to install anything extra in client PC to use MSMQ? Since
clients may not have all the XP components installed. Is there a way to
work around this issue if any?
2. Does the user need to be an admin to use the MSMQ since the app will
run under user permission?
3. Is there an alternative to MSMQ for passing commands around two
application?
4. Is there anything else I should be aware of when developing app to
use MSMQ??

Thanks in advance.

[Andy]

1. Yes, MSMQ isn't installed by default. Your application installer
(or ClickOnce installation) can list MSMQ as a requirement, but I'm not
sure it can automate the installation of such.

2. It depends I believe; I think the user can create private queues
only. I'm not 100% sure about this though..

3. To have the applications talk? Sure, you can open your own socket
and listen for events. Of course you have to be careful because it may
not be your 'sister' application which is sending data. Of course you
lose the advantage that MSM Queues can be transactional in nature; that
is, delivery is guaranteed.

4. Its fairly straight forward to send and receive messages using the
..Net framework. Getting the queues to forward to each other will be
the challenge; I've only used a queue on a single worktation, never had
to setup one queue to deliver to a queue on another workstation.

Good luck!

DBC User wrote:

Hi All,

I am going to develop two application which will talk to each other
using MSMQ. I have couple of questions

1. Do we need to install anything extra in client PC to use MSMQ? Since
clients may not have all the XP components installed. Is there a way to
work around this issue if any?
2. Does the user need to be an admin to use the MSMQ since the app will
run under user permission?
3. Is there an alternative to MSMQ for passing commands around two
application?
4. Is there anything else I should be aware of when developing app to
use MSMQ??

Thanks in advance.

[Alvin Bruney [MVP]]

the queue approach is a scalable approach that will work well in your
circumstance. about the only thing you need to be concerned with is
administration of the service and that is typically a none issue becuase it
requires very little effort. Another gotcha is that messages need to be
serializable because they will be pushed across the network. that's
typically only a problem when you are trying to move custom objects that
don't implement iserializable. you can take advantage of the queue
guaranteed delivery mechanisms as a bonus

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------
"DBC User" <db*****@gmail.comwrote in message
news:11**********************@m79g2000cwm.googlegr oups.com...

Hi All,

I am going to develop two application which will talk to each other
using MSMQ. I have couple of questions

1. Do we need to install anything extra in client PC to use MSMQ? Since
clients may not have all the XP components installed. Is there a way to
work around this issue if any?
2. Does the user need to be an admin to use the MSMQ since the app will
run under user permission?
3. Is there an alternative to MSMQ for passing commands around two
application?
4. Is there anything else I should be aware of when developing app to
use MSMQ??

Thanks in advance.