The Moth

# Code Snippets FAQ.

# Generic delegates in the framework.

# String Basics (and a few people come to mind that should go back to basics ;-)

# Katie Blanch (previously known as K. Schaeffer) contributes 3 interop articles on the netcf blog:
Extending GUI Functionality
Common Issues and Debugging Techniques
Log File Information

# One of the hot WM 5.0 topics is persistent storage.

# Hah! Recently I had an argument discussion on this topic so I hope my "opponent" reads this: Singleton or ExpensiveResourceSingleton.

In my previous post I linked to a class diagram that shows all the WM 5.0 managed namespaces. It turns out that diagram doesn't show the WindowsMobile.Forms namespace so here it is for your enjoyment:


Had I drawn it in a C# project all those 'As' would be ':' conforming to UML style but I'll refrain from going on about that again.

All of you know that Windows Mobile 5.0 was released in May at MEDC (Bill Gates keynote). Devices are expected to ship in Q4 this year.

From a general dotnet perspective, the most exciting thing about this platform release is that it exposes managed APIs! This is a first in both the mobile/embedded and desktop/server world. Maybe Longhorn will be the next, but for now WM 5.0 is the first and only one to do that.

What prompted me to share this is that already there are articles etc that refer to these APIs as being part of .NET Compact Framework v2.0 - they are not, they are part of the platfrom (which also includes CF 1.0 SP3 by the way). If you use netcf 2.0 to target a WM2003 or a WinCE 5.0 device, the APIs are not available. In contrast, if you use netcf v1.0 to target a WM 5.0 device then the APIs are available.

There is a lot of redundancy in my statements above but hopefully it will clarify the state of play (my fear is that this will become another common misconception similar to people talking about v1.1 of compact framework - when there is only v1.0 and v2.0).

The APIs I refer to are classes in the following namespaces:
Microsoft.WindowsMobile.PocketOutlook
Microsoft.WindowsMobile.Configuration
Microsoft.WindowsMobile.Status
Microsoft.WindowsMobile.Telephony
Microsoft.WindowsMobile.Forms

You can access them from Visual Studio 2005 once you download the WM 5.0 SDK and after you add reference to the relevant assemblies (same as namespace names with "dll" suffix)

Just to confuse things, there is a netcf 2.0 namespace with similar name: Microsoft.WindowsMobile.DirectX. If you are into game programming, check it out and also the article here

So, before I let you go back to your work, here is a link if you wish to find out more: recorded webcast & class diagram (the one missing is the Forms namespace which you can see here)

Oh, I almost forgot, if you like the new classes and would like to see them on earlier PPC versions (e.g. PPC 2003), check this out :-)

After delays upon delays I finally just made it back home from Dublin. Some photos from my talk are here (btw, if anybody wants me to talk at a user group or anywhere else, my new term of contract is that it must be followed by a “mouths-on” wine tasting lecture ;-).

So, since I haven’t personally caught up with any blogs this week, BLOTW redirects you to the Mobile Minute 105, 104 and 103.

If you are in Ireland, don't forget to come join us in Dublin this Friday for a unique wine & cheese tasting experience that follows my talk on Whidbey for devices (with an intermediate stop at the bar for some beer :-).

Register now! (We are flying out there tomorrow this time...)

This time round BLOTW is dedicated to Tech Ed Europe which was on last week. I was there in 2001-2002-2004, but sadly not this year.

Many blogs covered the event and some that caught my eye are here, here, here, here and here.

A Letter To The Terrorists, From London

If you are in England (UK), don't forget to come join us tomorrow in Horsham for free pizza and beer... and you might also learn something about the .NET Compact Framework :-)

It would be nice if you register, but previous experience indicates you can just turn up!

See you there at 18:30.

* Loads of useful tools. Bookmarking it here for its "TabletPC Indispensibles" (since I just ordered a Toshiba Portege M200 :-)

* Don't Fsck With Nerds

* Interesting perspective on the .NET vs Java debate

* Rules for better presentations
      (don't forget this Thursday to come see if I apply them)

The big news in my professional life is that I am leaving Trend/Honeywell after 6 happy years. We have both benefited from each other and I don't regret any of it. Trend, it's been a great ride, I wish you all the best and hopefully we'll cross paths in the future.

Here is the FAQ

Q. Were you fired, made redundant or otherwise asked to leave?
A. Quite the contrary, I resigned and seemingly leave a greater number of sad people behind rather than glad. I leave my current employer on excellent/amicable terms.

Q. Did you actively look to change jobs?
A. Not at all. I was professionally headhunted for a 3rd party. In fact it was real hard work for the agency to convince me to even consider thinking about looking elsewhere. Well done to them.

Q. Will you be working for a competitor?
A. No, not even staying in the same industry (BMS, HVAC). In fact I am transitioning from what is termed a "corporate developer" to being a "consultant".

Q. You are still working with .NET, right?
A. 100%, even more so than before. My new job involves working with Microsoft technologies *only* (same goes for every single one of my future colleagues).

Q. When do you leave your current employer and join your new one?
A. I finish here in mid-August. I start there in early-September. In between I'll go home to Greece for a much needed break.

Q. So where/who is your new employer?
A. It is based in London but my everyday working place will be wherever the client is. It is a company jointly owned by Microsoft and Accenture: Avanade (known for the Enterprise Library Application Blocks)

UPDATE: I no longer work for Avanade. I know that some of you searching for Avanade land here and then ask me for advice, I have none to offer regarding the company. Sorry and thank you.