Re: To C or not to C?
From: Ginny Caughey [MVP] (ginny.caughey.online_at_wasteworks.com)
Date: 07/07/04
- Next message: Mad Scientist Jr: "voice recorder error - Namespace cannot be found"
- Previous message: Bruce Eitman \(eMVP\): "Re: To C or not to C?"
- In reply to: Judd Bagley: "To C or not to C?"
- Next in thread: r_z_aret_at_pen_fact.com: "Re: To C or not to C?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 6 Jul 2004 21:59:50 -0400
Judd,
There's nothing wrong with your question, so don't expect flames here. ;-)
But the nature of the app you plan to create and your own previous
programming experience and preferences are important. Unless you are writing
devices drivers (which require C++) there really is no one correct answer.
I can give you some pros and cons for several Microsoft languages (and no
doubt others will fill in some gaps) but the final choice will have to be
yours since only you know what's most important to you.
eVB - easy to use but now obsolete. You can use it with current Windows
Mobile projects (and it's free), but it won't work with future Windows
Mobile devices.
eVC++ - if you can't do something with this tool (which is also free for
now), then it can't be done on Windows CE. It gives you the fastest apps and
the absolute most control, but it takes most of us longer to work in C++
than in other languages.
VB.Net or C# - although the languages are syntactically different, they are
functionally very similar. With VB.Net it's easier to avoid strong typing
(not usually a good idea), but with C# you can use pointers if you need them
(which you probably won't). They both use the Compact Framework and have a
growing following of free code such as the Smart Device Framework at
www.opennetcf.org. You can use either language from Visual Studio 2003 Pro
(or higher), which is the most productive development environment compared
with eVB and eVC++.
The desktop interface really makes no difference at all, since you can use
absolutely any Windows dev tool to create it that can make API calls. You
use the Remote API (Rapi) to communicate with the device, create files and
folders, copy or delete files, modify the device registry, launch apps,
etc., all from the desktop.
-- Ginny Caughey .Net Compact Framework MVP "Judd Bagley" <JuddBagley@discussions.microsoft.com> wrote in message news:4B8FB08E-BD28-432B-8948-DA59EBF76D6C@microsoft.com... > Before I'm admonished to RtFF or otherwise flamed, please know that I've made a VERY GOOD effort to avoid having to post this question. > > Let me make clear that I'm parachuting into this territory and, while I'm worthy of being called a power user, I've never developed for any device and thus have very little sense of context or understanding of terms of art or other colloquialisms. So dumb it down a notch, please. > > That said, all I need to know is where to get good OBJECTIVE advice on choosing a programming language for the application I'm going to develop (and you will all eventually buy) for WM devices. In my many readings, I've found developers to be more zealous about their preferred language than many people are about their chosen religion, and that they see the universe through that frame of reference. > > On the other end of the spectrum, Microsoft's publications seem to promise that EVERY option is a good one, in its own way. > > Therefore, I am offering no clue as to the nature of the project, only that I have one and need help making a decision. > > I will say this: the application will require a robust desktop interface - assuming that makes a difference. > > Please don't flame. Just a link or two would be great. > > Thanks! >
- Next message: Mad Scientist Jr: "voice recorder error - Namespace cannot be found"
- Previous message: Bruce Eitman \(eMVP\): "Re: To C or not to C?"
- In reply to: Judd Bagley: "To C or not to C?"
- Next in thread: r_z_aret_at_pen_fact.com: "Re: To C or not to C?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
