I'm a bit out of time nowadays and with upcoming exams, the expectations are not too much better. Though I would like to thank all who came - either to MS FEST or Aquarium - and at least share demos, which were presented on the sessions. I'm happy to answer any of your questions over e-mail.
A basic example of working with input and output ports and mainly how your work with periphals will usually look like - you write an driver representing a connected device and use it as an object. This example shows an easy driver for three LEDs used as a semaphore.
Required hardware: 3 LEDs connected with resistors to a board or module. Red on GPIO4, orange on GPIO5 and green on GPIO9 in this example (using Tahoe or Tahoe-II).
Shows: working with ports (OutputPort, InterruptPort), DispatcherTimer in console application, Timer, anonymous delegate, inheritance.
There was a really simple example on three rows introducing the serial port, which just sent a text to a external display. If you are used to the serial port in previous .NET Micro Framework version, don't forget the second one - call the SerialPort.Open() before use.
The external display used during the session has a command which allows to show any 1-bit bitmap. Using the new event in .NET Micro Framework 3.0 we show how to move all the WPF functionality in couple of rows to an external serial display, which does not have a built-in driver. This sample uses Micro XAML.
Required hardware: 2 buttons (up/down) for scrolling, external serial display (the one used during session was GW64x32C-K610A by Noritake Itron company).
Shows: working with the serial port, Micro XAML, new WindowManager.PostRender event for using WPF on external displays.
Showing the built-in accelerometer on the new Tahoe board. The application consists of a tiny red square, which moves on the display's bottom as you rotate the Tahoe board. This sample uses Micro XAML.
Required hardware: Tahoe-II
Shows: simple I²C register reading (without any library), DispatcherTimer outside the window, custom constructor in Micro XAML with a help of partial method.
The simples possible EWRDemo - the number of starts, without any classes this time, just pure integer.
This application reads JPG pictures either from resources or from a memory card when you insert some, and allows you to "slide" through them on the display. The program starts with a black sceen, first you need to tap to the pictures.
Hardware required: emulator or a board with touch screen support.
Shows: drawing on the display without WPF, working with touch screen from a console application, eventually the file system.
An easy example - shows arrows according to the gesture recognized on the touch display.
Required hardware: emulator or a board with touch screen support.
Shows: cathing the gestures events without using an InkCanvas.
A short loop which reads an image from the web and displays it on the display.
Required hardware: IP camera with HTTP access (the session used IP7131 by Vivotek), emulator or a board with ethernet support.
Shows: working with sockets to send a HTTP request and receive a response.
Simplified and modified SDK sample of a mouse device - turns your touch screen into a touchpad! Deploying, ev. debugging over TCP/IP or serial port required.
Required hardware: a board with touch display and an USB port (showed on Tahoe-II).
Shows: the easiest implementation of mouse in .NET Micro Framework possible.
WPF desktop application offering some web services by user's choice. For running this application on PC, you need to take the current DPWS libraries, decompile and modify them to work with .NET Framework. It's not that difficult, but unfortunately the final libraries cannot be distributed. Contains WSDL, which was used to generate both server and client code. WSDL was typed by hand.
Required hardware: runs on PC.
Shows: DPWS server at PC, and how to strip diacritics from text :-).
.NET Micro Framework application consisting of a textbox and four buttons (warning: buttons are only scratched, with minimal functionality). After startup, you can type into the textbox (SW1-4 on Tahoe), select part of the text and call any supported web service available on the network.
Required hardware: emulator or board with ethernet and touch screen support.
Shows: DPWS client, which looks for concrete web services on any newly connected device, calling web services, working with textbox and primitive button implementation.