Vista - WCF in Compact Framework v3.5 .... where'd everything go?

I was very excited to install the new Visual Studio 2008 RTM yesterday
because I am looking forward to consolidating communication technologies.

We created a Warehouse Management System that uses WCF between the Desktop
client and our Server, but uses MSMQ (version 3) between the Server and our
mobile clients (Windows CE v5.0).

I was disappointed to find the only two bindings that the new CF 3.5 offers
for the mobile world are BasicHttpBinding and the new
WindowsMobileMailBinding. The hope was to change the native MSMQ code in
favor of using WCF's MsmqBinding between the Server and Mobile client. Even
though MsmqBinding is missing from Mobile, the new WindowsMobileMailBinding
offers some of the same benefits ... the general idea of asynchronous Message
delivery that works well in the semi-connected mobile application world. The
biggest issue I can see is this setup requires Exchange (it acts as a relay
when using this binding). I'm as much a fan of Exchange as the next guy, but
this seems to unneccessarily add expense, complexity, and a reduction in
reliability ... versus using MSMQ.

Also, it appears that callbacks, transactions, sessions, and all the other
bindings are gone too. The last item is that mobile WCF is relegated to
simply Message level transport and not the full Service Model that WCF
offers. Now, with all that said, and being mindful that this is still
"mobile" development which means take whatever the desktop frameworks have
and reduce by 90%, I understand and expect mobile to be "handicaped" a bit.
But, does anyone know what the WCF team's plans are going forward for
mobile?? Any chance MsmqBindings, Sessions, callbacks, Fault Contracts, Data
Contracts, etc., etc. will be added down the road?

Although it might not be perfect, it is a step in the right direction.
Thanks guys for taking WCF mobile.


--
Stay Mobile