Windows Mobile development: C++ or C# -- which one is better? why?

Question

While doing Windows Mobile development, which language should I use? C# or C++ or something else? Why one is better than others?

Answer 1

Hi,

It depends what you're coding.

Making native calls to the OS are possible via P/Invoke from C#, but extensive use is probably easier via native C++. You'll also require C++ for using some hardware that has not been wrapped by the Compact Framework.

Most hardware (GPS, camera, etc.), is available via CF. If you're working with a Win Mobile 6.x device, you're probably better off with C#. In addition to hardware, Pocket Office's (POOM) object model is also available to C#, so you can integrate with it.

It's worth noting that most references to Windows Phone 7 refer to managed code and the possibility of Silverlight. With Silverlight in the mix, you'll have to code with C#.

Unless your app is high performance or is extremely miserly with memory, use C# or VB.NET.

Scott

Answer 2

It depends on task mainly.

c++ has following pros/cons:

• Direct access to resources, faster programs
• Can access very deep OS parts, not needed for high level applicaiton
• harder to develop and requires to manage resources by developer

C#:

• Runs under virtual machine (CLR), that's why is slower
• Faster and easier application development
• Rich build-in library

Answer 3

It depends.

At least present a specific use-case. And possibly use SO search? :)

http://stackoverflow.com/questions/708484/c-or-c-to-program-mobile-barcode-device

Edit: Apparently others were faster to the draw, and gave more articulated answers. Nevertheless, I still recommend reading the above SO thread.

Answer 4

There is no right answer for this, becasue there is no one-size-fits-all "better" definition. If you know C++ and have a lot of C++ code assets already, C++ sure looks appealing. If you know c# and not C++, then C# sure looks appealing.

C++ applications load faster, but for many applications, that's not relevent. C# applications can certainly be written faster, but they also don't have determinism. I'd never even attempt a UI in C++ any longer, nor would I think about doing database access in C++. I wouldn't write a driver in C# though, or a shell extension.

Generally speaking, most solutions I've ever delivered were a mix of the two. C# has its strengths. It's fast to write, easier to debug and unit test, hard (though not impossible) to create leaks and for some operations (like data access or XML parsing) it's just easier.

C++ has its strengths too, like speed of execution (though C# can be made to go just as fast for many things), determinism and the ability to plug in to things that want native entry points.

So my answer? You need to know both, and likely write your solutiuon using both. The percentage of each you end up using depends on what your end goal is.

Answer 5

From my experience it is easier to start with c#, and if the api provided by the compact framework is enough for you then you are ok.

On the other hand if your project is somewhat complex, or if you want to do something that is not in the compact framework you may end needing to create a helper .dll in c++. Even in this case you maybe good doing your main program in c#, and programming helpers dll in c++.

If you go directly to program in c++ you may benefit from the fact that you have a raw performance better than c#, which is good if you are doing a game.

But you will also suffer more from the limitation of windows mobile OS. Like a maximum of 32MB per process, or that all .dll share the same address space.

So in the end it really depends on what are planning to do and the experience you have.