Windows Mobile Team Blog

I'm ashamed - so far I haven't moved beyond copying class files (and there's no reason at all why I couldn't use shortcuts. So I ask myself "Why don't I?", and I answer "Because you're lazy and couldn't organise an indecent act in a house of ill repute')

A couple of good postings on developing applications for the compact framework and the full framework http://www.zen13120.zen.co.uk/Blog/2004/09/share-code-if-fullframe_17.html http://www.zen13120.zen.co.uk/Blog/2004/09/retargetable-256.html Swoosh! uses the same "business logic" dll (exact same binary) and then different exe UIs (one compact framework and several full framework) on top of that. I definitely agree that in general it isn't worth it to use the same exe. Who wants a Pocket PC UI on a 17" monitor? I had heard of the conditional compilation constant approach before but wasn't comfortable enough to use it at the time I started Swoosh!. This article lays out more of how to set things up. I think if I had done it that way, it would have saved a lot of time copy and pasting stuff back and forth. via Windows Mobile Team...

i do the same. it would be nice if the project types had a directive such as FULL_FRAME or CF already defined that we could switch off of in our code

Speaking of cross platform, don't forget reusing your C# code for use with Mono supported platforms. This would add Linux into the mix too!

But related to .NET CF development, it is really darn easy to work with if you have done any .NET on the desktop. From my experience, most of my code was almost a no-brainer to port. The only thing that really required retraining and reading was getting the UI to look nice on such a small screen.