August 2003 - Posts
Jason Dunn, of pocketpcthoughts.com, has conducted some extensive testing to determine if Windows Mobile 2003 is really faster. Here is the test. It's nice to see some extensive tests like this. I found it also interesting to note that in some cases going from Pocket PC 2000 to Pocket PC 2002 certain things slowed down (and yes, an instance of a slow down going to 2003 from 2002). :/
I give Jason kudos for obtaining a special build of Windows Mobile 2003 that is for the iPAQ 3650 (no, this will not be released to the public). I actually don't mind not upgrading my iPAQ H3650 (it is running PPC2002, upgraded from PPC2000); I plan on keeping it as a test device once I get a new device in October. I agree with Jason that Microsoft made the correct decision in concentrating on improving ARM performance under Windows Mobile 2003, and not making any XScale optimizations. (my own opinion <insert_employer_disclaimer_here> is that if your PPC app perf is really sucking *that* bad, either you are doing something incorrectly [go evaluate how you are doing something], or you are doing something inappropriate on this platform [re-evaluate your architecture and see if something is a candidate to be moved off to a PC or server, or can be accomplished through different means])
As I've told people, putting your app on Windows Mobile 2003 will give it a performance boost (just like running your database in SQL Server 7.0 on WinNT 4.0 and Win2k, back in the day), and to couple that with a newer device (think PXA255 @400MHz, more RAM and ROM), you app will show a noticable perf boost.
p.s. Maybe that SQL Server 7.0 reference was a bad one.. :/
Office 2003 hasRTM'd
Intermec (makers of ruggedized Pocket PC and Tablet PC devices) is now shipping devices with Windows Mobile 2003 *applause*
I did a search today on GDN for .NET CF projects, and was pleased to see a few of them
I saw Jason's post about .NET CF dev without VS.NET...
And for my two readers, I've been slammed at work, and this week I'm on vacation (enjoying Hilton Head Island , SC),which is why no posts as of late. I don't post that often anyways, in the interest of keeping my blog 'clean', and to that end, I support Greg's comments about signal/noise ratios. I am getting a .Text-based personal blog set up to handle all the stuff I'd like to post here, but do not feel is appropriate.
Lastly, in a bit of the_pot_calling_the_kettle_black, I'd like to send out my congratulations to a co-worker (KrisB) who is celebrating his 6th anniversary today. My wife and I are celebrating our 4th anniversary today as well (woohoo!). I'm looking forward to a lovely evening at one of Hilton Head's fine dining establishments.
This article compares some of the main features of Windows CE.NET 4.2, Pocket PC 2002, and Windows Mobile™ 2003 software for Pocket PC. It is designed to provide customers with a better understanding of the commonalities and differences between the platforms and explain the roles each play in Microsoft’s ongoing mobile and embedded device strategies.
The Windows Mobile™ platform is the lead Microsoft offering for mobile handheld computing devices and applications, including personal digital assistants (PDA). Standardization of both hardware and software requirements has allowed the Pocket PC to provide an optimized mobile handheld experience while supporting third-party application development. Windows CE .NET is designed to target a broader range of embedded devices. Given the array of embedded devices that may be created using Windows CE .NET, there are no standardized hardware or software requirements. The technologies in this article are grouped in nine major categories, based on common functionality.
The Windows 2000 Authorization Manager Runtime is a Windows 2000 Server version of the Windows Server 2003 Authorization Manager role-based access control API.
Windows Server 2003 family operating systems introduced the Authorization Manager Role-based access control framework which includes the Authorization Manager API and Role-based MMC snap-in Administration UI (Authorization Manager Snap-in UI is only available on Windows Server 2003 family operating systems and on the Windows Server 2003 Administration Pack for Windows XP.) The Authorization Manager API provides a simplified development model in which to manage flexible groups and business rules and store authorization policies.
Using the Windows 2000 Authorization Manager Runtime you can build server applications to use the Authorization Manager Role-based access control model that run on Windows 2000 Server family operation systems.
COOL! I can now use Authorization Manager on Win2k (not that I don't prefer it on Win2k3..but if I'm stuck, er, using, Win2k I have this at my disposal.)
"Watch Neil Enns and Ori Amiga present a cool demo of building a weather application in less than five minutes using Visual Studio .NET 2003 and a next generation Smartphone device"
This I've got to see, as I thought that only Whidbey could to .NET CF SmartPhone development.. hmmm