Hello,

Is there an alternative approach to MSMQ for delivering messages? I am
planning to develop an app which I don't want clients to install MSMQ
(or do anything otherthan install my app). I was want to pass messages
between two programs and my first approach was MSMQ and it worked
perfectly and then I found out MSMQ is a seperate win component and is
not installed by default.

I am looking at writing files and implement filesystemwatcher method.
Is it a viable solution??

Thanks in advance.

You can write files, or you can use a "no install" database such as SQLite.
As long as you have some notification / polling mechanism operating, you
should be able to come up with something that works. MSMQ, however, if you
need a robust solution, is preferable.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com




"DBC User" wrote:

> Hello,
>
> Is there an alternative approach to MSMQ for delivering messages? I am
> planning to develop an app which I don't want clients to install MSMQ
> (or do anything otherthan install my app). I was want to pass messages
> between two programs and my first approach was MSMQ and it worked
> perfectly and then I found out MSMQ is a seperate win component and is
> not installed by default.
>
> I am looking at writing files and implement filesystemwatcher method.
> Is it a viable solution??
>
> Thanks in advance.
>
>

DBC User,

Honestly, why not make it a prerequisite that they install MSMQ? Using
files in that manner is pretty gnarly.

If anything, you could always use sockets.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- (E-Mail Removed)

"DBC User" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello,
>
> Is there an alternative approach to MSMQ for delivering messages? I am
> planning to develop an app which I don't want clients to install MSMQ
> (or do anything otherthan install my app). I was want to pass messages
> between two programs and my first approach was MSMQ and it worked
> perfectly and then I found out MSMQ is a seperate win component and is
> not installed by default.
>
> I am looking at writing files and implement filesystemwatcher method.
> Is it a viable solution??
>
> Thanks in advance.
>

If I make MSMQ as a pre-requite, the client need to have Widows CD?
Nicholas Paldino [.NET/C# MVP] wrote:
> DBC User,
>
> Honestly, why not make it a prerequisite that they install MSMQ? Using
> files in that manner is pretty gnarly.
>
> If anything, you could always use sockets.
>
> Hope this helps.
>
> --
> - Nicholas Paldino [.NET/C# MVP]
> - (E-Mail Removed)
>
> "DBC User" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hello,
> >
> > Is there an alternative approach to MSMQ for delivering messages? I am
> > planning to develop an app which I don't want clients to install MSMQ
> > (or do anything otherthan install my app). I was want to pass messages
> > between two programs and my first approach was MSMQ and it worked
> > perfectly and then I found out MSMQ is a seperate win component and is
> > not installed by default.
> >
> > I am looking at writing files and implement filesystemwatcher method.
> > Is it a viable solution??
> >
> > Thanks in advance.
> >

DBC User,

I have never needed the Windows CD to install MSMQ on my machine after
installing Windows XP SP 2. I would just go to the windows components and
click on it, and it would install, no CD required.

However, it's not unreasonable to expect people to have the CD. After
all, they bought it, no?

--
- Nicholas Paldino [.NET/C# MVP]
- (E-Mail Removed)

"DBC User" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> If I make MSMQ as a pre-requite, the client need to have Widows CD?
> Nicholas Paldino [.NET/C# MVP] wrote:
>> DBC User,
>>
>> Honestly, why not make it a prerequisite that they install MSMQ?
>> Using
>> files in that manner is pretty gnarly.
>>
>> If anything, you could always use sockets.
>>
>> Hope this helps.
>>
>> --
>> - Nicholas Paldino [.NET/C# MVP]
>> - (E-Mail Removed)
>>
>> "DBC User" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> > Hello,
>> >
>> > Is there an alternative approach to MSMQ for delivering messages? I am
>> > planning to develop an app which I don't want clients to install MSMQ
>> > (or do anything otherthan install my app). I was want to pass messages
>> > between two programs and my first approach was MSMQ and it worked
>> > perfectly and then I found out MSMQ is a seperate win component and is
>> > not installed by default.
>> >
>> > I am looking at writing files and implement filesystemwatcher method.
>> > Is it a viable solution??
>> >
>> > Thanks in advance.
>> >
>

I agree but what I am trying to get at is to make my app more easy to
install and easy to use. But I will explore this option.
Thanks again.

Nicholas Paldino [.NET/C# MVP] wrote:
> DBC User,
>
> I have never needed the Windows CD to install MSMQ on my machine after
> installing Windows XP SP 2. I would just go to the windows components and
> click on it, and it would install, no CD required.
>
> However, it's not unreasonable to expect people to have the CD. After
> all, they bought it, no?
>
> --
> - Nicholas Paldino [.NET/C# MVP]
> - (E-Mail Removed)
>
> "DBC User" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > If I make MSMQ as a pre-requite, the client need to have Widows CD?
> > Nicholas Paldino [.NET/C# MVP] wrote:
> >> DBC User,
> >>
> >> Honestly, why not make it a prerequisite that they install MSMQ?
> >> Using
> >> files in that manner is pretty gnarly.
> >>
> >> If anything, you could always use sockets.
> >>
> >> Hope this helps.
> >>
> >> --
> >> - Nicholas Paldino [.NET/C# MVP]
> >> - (E-Mail Removed)
> >>
> >> "DBC User" <(E-Mail Removed)> wrote in message
> >> news:(E-Mail Removed)...
> >> > Hello,
> >> >
> >> > Is there an alternative approach to MSMQ for delivering messages? I am
> >> > planning to develop an app which I don't want clients to install MSMQ
> >> > (or do anything otherthan install my app). I was want to pass messages
> >> > between two programs and my first approach was MSMQ and it worked
> >> > perfectly and then I found out MSMQ is a seperate win component and is
> >> > not installed by default.
> >> >
> >> > I am looking at writing files and implement filesystemwatcher method.
> >> > Is it a viable solution??
> >> >
> >> > Thanks in advance.
> >> >
> >