NET/C# queued component and C++ client

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Yurii - 14 Jul 2004 21:36 GMT

I have a C# queued component registered on 2000 (had to install .Net
framework there). Now I'm calling CoGetObject() in C++ client getting
valid pointer for queued object and everything looks fine except there
is no messages in the queue after method call (queued component is not
started). What might be a problem?

Reply to this Message

Tomas Restrepo \(MVP\) - 15 Jul 2004 02:20 GMT

Yurii,

> I have a C# queued component registered on 2000 (had to install .Net
> framework there). Now I'm calling CoGetObject() in C++ client getting
> valid pointer for queued object and everything looks fine except there
> is no messages in the queue after method call (queued component is not
> started). What might be a problem?

What do you mean by "there is no message in the queue?" Remember that if the
receiving application is not started already, it will not be started when a
message is sent. Instead, it will just be stored in the queue. You'll need
to start the COM+ app yourself.

Also, make sure your com+ application has the correct settings needed to
activate the queue listener.

Signature

Tomas Restrepo
tomasr@mvps.org

Reply to this Message

Yurii - 15 Jul 2004 16:42 GMT

Pardon my English.. I meant there is no messages in the queue (stored,
appeared, whatever). And all settings are set up correct because
absolutely same example works on XP with C# client.

Reply to this Message

Rate this thread:

NET/C# queued component and C++ client

Free Magazines