I'm primarily a Ruby developer but, in my spare time I like to build things for the Pocket PC using the dreaded, cursed and generally reviled VB.Net.
As I said on patrickonrails, I am not an OS elitist.
I think most of those guys need their heads examined because of their presumption that one OS is best for everything.
And besides I like to build things for my iPaq 1950. I already have Scheme, Python, and a semi functional Ruby install working.
So, I'm going to talk about where I am today with regards to iPaq development.
My core building system is a Windows Vista 64 bit Ultimate Home edition.
MS 64 bit, is a weird beast. It's generally hard to determine which applications are going to work right out of the box and which ones are going to be a big Fail.
Next, I'm using the SharpDevelop ide as it has support for the Compact .net framework. I used it quite a bit on the Windows XP but, currently I'm having some problems with getting it to run on Vista.
At this very second, I am downloading the Windows Mobile 5.0 PocketPC SDK in the hopes that it will install some weirdo dll that I need.
Subscribe to:
Post Comments (Atom)
Well, that was a big fail.
ReplyDeleteApparently some form of Visual Studio needs installed.
Off to download the CTP version of VB.Net.
Oh yeah. A few other things:
ReplyDelete1. Vista and Embedded VB fail even bigger. Use a VM of XP
2. #develop doesn't support the compact framework in their form designer. Which, frankly is pretty stupid. They could have a nice market for Windows Mobile developers that, in typical OSS community fashion, they throw away.
The only shortsightedness I see with the OSS community is that they usually fail when it comes to understanding how they might undercut the cathedral's methodolgies and market share.
The other minor quibble is that they tend to be a bit fanatical.