O2 Exec etc... programming IDE

[VZ800]

I use Visual Studio 6 and 2005 at work, and was wondering what development environment you use for writing applications etc, for the Exec. I installed WinCE C++ v4.0 yesturday and the .exe built for the ARM processor wouldn't run!

[cgrillo]

Visual Studio 2003 or 2005 work fine.

(you can get the "academic" version if you are a student for less than £50)

[Rudegar]

with 2003 you have to make smartdevice projects and write them in c#
in 2005 you should be able to do MFC and win32 in c++ as well

[VZ800]

Thanks.

[levenum]

Which ever IDE you use, you need to download Pocket PC SDK from MS (it's free) for Window Mobile 5.

You can also use eVC 4, but you need to install SP 4 for it, and PPC SDK for Windows Mobile 2003 (it won't recognise WM5 SDK).

[VZ800]

Sorry to be a pain but I have not written software targeted at WinCE/WM before.

I have installed eVC4, Microsoft Pocket PC 2003 SDK, SP3 and SP4. I can debug with the Pocket PC Emulator fine, but when I try to debug or install in release mode on the O2 Exec (which is connected) I get the following warning dialog: "CE platform pocket pc 2003 does not match remote os version 501". :?

I do not want to write software for the PPC using .NET (although I write in C# at work, as well as MFC/ATL C++), as in my opinion the PPC isn't fast enough for managed code. So how can I write apps' for the O2 Exec using eVC4 :?:

[levenum]

Hi VZ800!

You are right about .NET, those apps are more sluggish then native code.

Don't worry about the warning, just click yes, then you going to get another warning, something about CPU type, click yes on that one two.

The eVc bitches because it's not familiar with WM5 devices, but your program will run fine. In fact, I used eVc 3, to write programs for WM5 that were backwards compatible with WM 2002 and they worked fine (although eVc 3 can't connect to the device so I had to copy the exe manually).

The debugger should work as well, though I try to avoid it since it some times takes a long time to connect.
If all you need is some debug prints, no watches or brake points, you might be better off writing to a file with the old fopen, fprintf, funcs. which come in both ASCII and Unicode (wfprintf) versions.

Good luck!

[VZ800]

Thanks, I'll give it another go tomorrow.