John
Tue Apr 05 11:54:10 CDT 2005
One problem with MSMQ for this is that the current version of the .Net CF
does not support System.Messaging which means that you would have to write
P/Invoke wrappers to get at MSMQ access. MSMQ is probably a more eloquent
way of handling interproc that the shared database, however, but not sure if
it's worth your dev time.
.Net does not in general have a good interprocess communication mechanism on
CE in general.
--
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation
Check out the new CE Networking Team Blog at
http://blogs.msdn.com/cenet/.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights
reserved.
"Tony Hudson" <TonyHudson@discussions.microsoft.com> wrote in message
news:53477EFB-75C4-4043-BE0B-2990E0F9C2CF@microsoft.com...
> We have a "suite" of applications that run on a pocket pc. We have
> implemented inter process communication using a database for conveying
> messages and data between the applications, however would MSMQ be a more
> suitable solution as we are porting these eVB applications onto the .NET
> CF?
> If so can someone point me to a good reference for this type of
> configuration.
>
> --
> Tony Hudson