Mobility Touchdown Team Blog : lab

New Content coming for FY08

lokeuei — Mon, 27 Aug 2007 20:55:00 GMT

We're currently heads down working on updating the existing content to include current technologies such as Windows Mobile 6, the new SDKs, Visual Studio 2008 and .NET Compact Framework 3.5. We should have the complete 3 day hands-on workshop and alternative 1 day seminar style content by October.

Mobility Touchdown Argentina kicks off today!

lokeuei — Tue, 08 May 2007 20:06:00 GMT

Q4Tech and Ronald Armas (Architect Evangelist) in Latin America kicked off the first in the series of 3 mobility touchdown workshops to be held in Argentina, Peru and Colombia.

Mobility Touchdown workshop content now available for download

lokeuei — Tue, 01 May 2007 09:27:00 GMT

Thanks to Q4Tech.com for providing the FTP site. You can now download the entire 3 day hands-on workshop installer that correctly installs the LAB files, Databases required, sync configuration and slides. You also get a pre-requisite document that describes the machine configuration before you can install this workshop AND the post-install guide.

~~Download it here:~~

~~ftp://201.216.198.25/~~
~~Username: guest~~
~~No password.~~

* UPDATE: new download link here : http://www.q4tech.com/mobilitytouchdown/ *

Error in Developer Support Cards

lokeuei — Fri, 27 Apr 2007 20:58:07 GMT

Thanks to the guys at the Chicago workshop, they found out that the URL on the GREEN Developer Support cards have a problematic URL.

The correct URL should be :

http://www.microsoft.com/windowsmobile/developers

The "s" was missing from the URL printed on the cards.

Calling Managed code from Native

lokeuei — Wed, 25 Apr 2007 02:22:00 GMT

This was a question from Zain Ghani of FedEx during the Memphis workshop.

Q: How do you call a managed assembly from native C++? Do you have a sample?

A: There’s no direct convention to do this. We support calling native code *from* managed code, but you can’t just call a managed app directly from C++. Going from managed to native is provided via P/Invoke and COM Wrappers (NETCF 2.0).

That said – there are some creative ways to effectively call a managed app from a native app. One way is to use something like the MessageWindow class. This class basically allows you to pass simple windows messages from native to managed, so you as long as the data is simple, you can pass it that way and send notifications to your NETCF app. You can also use something like a named event -- trap it in the managed app and fire it from native code –or - you could use MSMQ to pass data around. There are also ways to use the COM wrapper you build NETCF 2.0 to use delegates to call back into the managed code. There are a number of ways to creatively get data from a native app into a managed app, but we don’t have a direct way to simply make a direct function call from native to managed. There have also been some 3rd party/community libraries that attempt to do this (e.g. – Mirror, etc.)

http://msdn2.microsoft.com/en-us/library/aa446497.aspx
http://msdn2.microsoft.com/en-us/library/aa446485.aspx
http://samples.gotdotnet.com/quickstart/CompactFramework/doc/messagewindow.aspx

Thanks to Reed Robison from the Mobility Premier group.

App.config for final lab

timheuer — Tue, 17 Apr 2007 23:08:00 GMT

During the Las Vegas lab, we found that there was a missing file that didn't get applied with the "putting it all together" lab in the final step. Attached to this blog post is the missing app.config for that lab portion.

Apologies it wasn't there!