MSMQ on PPC 2003 Installation

  • Thread starter Thread starter Steve B.
  • Start date Start date
S

Steve B.

Hi,

I want to test MSMQ capabilities on a PPC 2003 device.
I use VS 2005 Final with CF 2.0 to build a simple app.

When I launch the application, I get an error telling me that MSMQ is not
installed on my device.

After some search, I've seen that I need to install a redistribuable package
to have MSMQ on the device.
I can't find this package, where it is?
An article told it is in Program files\Microsoft Visual Studio 8\Smart
Device\SDK\SDKredist... but this folder does not exists, and in VS 2005
setup
I did a full installation....

Thanks for any help

Steve
 
There are some specific steps needed to install and register MSMQ once you
have installed the required files. Can I suggest this series of posts from
Mark Ihimoyan as these contain lots of detail on System.Messaging in .NETCF
2 and installation issues:-
http://blogs.msdn.com/ihimmar/archive/2004/06/08/151326.aspx
http://blogs.msdn.com/ihimmar/archive/2004/06/14/154909.aspx
http://blogs.msdn.com/ihimmar/archive/2004/06/14/154911.aspx
http://blogs.msdn.com/ihimmar/archive/2004/06/26/166914.aspx

Peter
 
Message will mostly be transported over GPRS connection.
But, if user is at office, sending message over Active Sync (cradle or
bluetooth) or wifi should be great...


"Miguel" a écrit :
 
Well you should be aware of the fact that the desktop passtrough (for
non Mobile 5 devices) isn't robust enough to use it in combination with
MSMQ.
Desktop passthrough can't provide the required stability.
 
What can happen ?
If a message transfer fails, the user will have to un craddle then craddle
again, don't he ? No message will be "lost".

Actually, 95% of transfers will occurs out of office, so using GPRS, and
then, can't be sure that the connection will remain stable.

Do you think MSMQ is not a good solution for our application ?
It is a typical ordering application, with a local db (sql mobile probably),
the user types orders and send them in a queue. Once a day the user
"synchronize", so actually send new orders, and get client db modifications...

Steve
 
Hi Steve,
Just a quick note about MSMQ and Activesync (Version 3.8 at least). Because
the activesync uses a private IP address it is not possible for it to be
routed accross a network in the usual manner. Outgoing is fine but the return
path will fail as MSMQ operates is a discnnected as opposed to connected
format (ie it does not establish a TCP/IP Tunnel and then send and recieve
it's data, it connects, sends data and then disconnects). If you MQ target q
is on another device other than the workstation directly connected to the
device it is unlikly that 2 way comms will be established as a result ACK
messages cannot be returned to the transmitting device etc.

We have used activesync to provide a reliable transport mechanism using a
local MQ managers on machines that dock handheld devices and it is
(Reasonably) fast and very reliable. Activesync n our case simply acts an
endpoint that allows the device to establish and maintain a connection to the
workstation.

To get to this point we had to use a Serial dock and a local PC RAS
connection in order to establish a "Real" network link.

HTH
Myles.
 
Back
Top