   Developing for Windows Mobile 2003
  Hi. I have a question. I am thinking about getting this PDA Phone with Windows Mobile 2003 and develop applications for it. You have a couple languages to choose from for development. The one I'm looking at is eMbedded Visual C++ 4.0 Now, my main question is: I am a C programmer, not C++, Would a C programmer be able to program for this OS via eMbedded Visual C++ 4.0? If so, would there be any restrictions or cons that would not be beneficial after all?Thanks,xeddiex.   
  Even though the name implies that embedded Visual C++ is just  C++ IDE, in reality it's not. You can use it to create and compile C programs as well without any problems.   ;Quote:Original post by xeddiexHi. I have a question. I am thinking about getting this PDA Phone with Windows Mobile 2003 and develop applications for it. You have a couple languages to choose from for development. The one I'm looking at is eMbedded Visual C++ 4.0 Now, my main question is: I am a C programmer, not C++, Would a C programmer be able to program for this OS via eMbedded Visual C++ 4.0? If so, would there be any restrictions or cons that would not be beneficial after all?Thanks,xeddiex.evc++ 4 is based off of vc++ 6, so essentially all it IS good for is C programming, the C++ portion is garbage.However, I highly suggest you look into the .NET compact framework. The entire system is so streamlined and simplified that it's really hard to believe something like it is available.   ;  I remember an interesting quote about Windows mobile  about its pros and cons from a while back, and "remember" I mean "made up right now".The mains pros and cons of windows mobile are as followsPros: Windows whereever you goCons: Windows whereever you goNow that the pleasantness is out of the way, I'll actually try and make a productive post. Your main problem developing for a mobile platform isnt going to be the OS itself, but rather the phone's technical limitations. Phones dont have a whole nutload of power behind them, so you'll find yourself optimizing. A LOT.Anyways, you "should" be able to work with Embedded with something that, worse case scenario, resembles C. I say "worst case" in the sense that you may have to modify some C code to work with a compiler designed specifically for C++. I'm not really sure though, but you shouldnt have too many problems.Quote:Original post by capn_midnightevc++ 4 is based off of vc++ 6, so essentially all it IS good for is C programming, the C++ portion is garbage.However, I highly suggest you look into the .NET compact framework. The entire system is so streamlined and simplified that it's really hard to believe something like it is available.*points and laughs*   ;  Heh, it's all good then. And yeah, I heard vc++ 6 sux with c++ but it's A'OK with C89, so I feel lucky [wink]. The .Net stuff really sounds interesting and I really want to start on a language such as C# but right now I don't have so much time for that - plus; I've spend over 2 years learning C so I would feel really bad and like a waste of time if I just quit C and went to some other langauge. A couple more years and I'll move on (or forcibly) I guess...Thanksxeddiex.   ;  After I got my Pocket PC, Microsoft released their Compact .NET Framework.  I never really got around to playing around with it until a while ago when I put together Pocket Tic Tac Toe.  Visual Studio comes with a nice template to make compact .NET framework applications.  Very, very, easy to use and create with.   ;Quote:Original post by Rob LoachAfter I got my Pocket PC, Microsoft released their Compact .NET Framework.  I never really got around to playing around with it until a while ago when I put together Pocket Tic Tac Toe.  Visual Studio comes with a nice template to make compact .NET framework applications.  Very, very, easy to use and create with.indeed, when my Axim first arrived at my house, I had it plugged in, charged a wee bit, and running a simple Pong game that I had coded while I was waiting for it to charge. All told about 10 minutes. I was floored. As long as you know C# (or whatever language you're coding in at the time), and are familiar with the .NET framework, the .NET compact framework is no different (actually, it excludes some portions of the framework, but I've not encountered any problems with it yet, I don't use those portions anyway).   