Ho Ho Ho ... Happy Holidays, Gurus ... and perhaps you can help me with this problem.
I have a little app which is the Tip of the Spear for a larger app to come. The app involves moving messages around among a number of lesser apps, each having a dedicated Message Queue.
The design is such that there is one message 'traffic cop' who oversees (and directs) the message flow, and there are 'n' lesser apps that connect to it via their dedicated Message Queue. For instance, a typical session might include the traffic cop distributing messages between a translator app, a logger app, a device-controller app, etc.
Ultimately, the design is such that the 'traffic cop' who directs the flow of messages will be implemented as a Windows Service, while all the other little apps will be conventional Windows 'forms' appplications.
OK - enough 'background' let's get down to business.
The 'traffic cop' was loaded as a Windows Service for the first time just moments ago and died almost immediately.
The existing queue had been 'opened' with a call to the MessageQueue constructor, apparently successfully, but died on the very next statement, a MessageQueue 'Purge' statement.
An exception was thrown and the accompanying message is "Access to Message Queuing system is denied."
However, the 'Traffic cop' performs just fine when implemented as a conventional Windows application - indeed, it has been running reliably for several days as a conventional Windows app.
So, bottom line: Why does it die when implemented as a Windows Service, and what, if anything, can be done to get around Microsoft denying me access to the Message Queueing system ?
Thanks for your help, troops.