August blog entry ;-)


I just realized that August is practically over, and I haven’t produced a single blog entry this month … got to change this immediately.


Well, I’ve spent the last three weeks at home, recovering from knee surgery and an accompanying inflammation. Not a nice thing to be forced to use crutches when you’re used to be running around. But it’s getting better by now, I can at least walk again, and I’ll be back in my office next Monday – finally! (You don’t get to be very productive at home when two little kids are competing for your attention all day long…) On the following Saturday, I’ll enter a plane for L.A., going to the PDC – can’t wait to get there again, PDC ’03 was such an exciting thing, hope this one will be a huge success again.


At home I spent some time playing with Platform Builder for Windows CE 5.0 (great!). I’m going to dive into embedded topics a little deeper in the future, so I have to look at a lot of things that I only had superficial knowledge of up to now.


On that occasion I (again) realized that there is currently (Beta 2) no Windows CE 5.0 emulator image in Visual Studio 2005, though there is a project template for that platform. A friendly soul inside MS pointed me to the possibility of building my own (ARM) WinCE 5.0 image in Platform Builder, but since I’m not yet very experienced doing that, he provided me with a “home-grown” image for the new device emulator. Great stuff!


Which brings me to a question to you, dear reader: Do you think we (MS) should provide such an emulator image (CE 5.0), be it by RTM or afterwards? Would you benefit from that, would it make your life or certain decisions easier? If so, why? Or are you creating your own images anyway? Please give me feedback on that if you don’t mind. Your opinion counts.

Comments (5)

  1. Hello Frank,

    yes, I think an emulator image for Windows CE 5.0 would help develop software for this new Operating System. As you know, our company deals with software for embedded devices, so we need a lot of devices we can debug / test. An emulator woul save costs, even though some device specific functions need to be tested on a real device.

    I hope you get well soon.

    Best regards,

    Stephan

  2. Yes, i think an emulator is essential for developing :

    – In case you have currently no device (does not work etc.)

    – If you cannot establish a connection between VS.NET and a physical device (debugging on a device is sometimes tricky with CE.NET)

    – If you want to be sure that a behavior is not device-specific, but by design of Windows CE.NET 5.x

    That are some reasons 😉

  3. Daniel Moth says:

    It is essential!

    1. It is a shame you are delaying this for after RTM. If you do a poll you’ll find that 80% of the developers targeting a CE 5.0 device do not have the device yet! Migrating from 4.2 to 5.0 is no picnic and an emulator out of the box would have helped parallel development of app and OS.

    2. Even with a physical device, connecting to it is a hit and miss with the Beta and I am not sure this will change later. Look at the unanswered queries in the forums and ng on CE 5.0 connectivity.

    3. Generating a PB emulator image for VS2005 is even trickier than what it was with VS.NET2003 (i.e. we couldn’t make it work). Even if you can generate an SDK/emulator, it will be x86 and not arm like the new emulators in VS.

    4. Not everyone that needs to test something on CE 5.0 has access to a device. Think demos and supporting the community while not personally doing it as part of the day job.

    5. Although support for CF 1.0 apps (on PPC2003/SP2003) is offered in VS2005, there is no support for CF 1.0 with CE 4.2 (which technically is no different so it must have been a matter of resources). This kind of forces devs to go with CE 5.0 so give us the emulator 🙂