eMbedded Visual C++

Articles at Pocket PC Developer Network

• Strings on a Pocket PC, Unicode and ANSI
  September 26, 2001. All WinAPI functions on Pocket PC work with Unicode strings. I think that it was a greate idea but... But legacy in our minds. Developers get into the way of using ANSI string developing for desktop. This article describes some common problems.
• QA: How to use STLPort on Pocket PC?
  October 16, 2001. I know that STLPort is one of the best portable STL libraries. How can I use STLPort with my embedded Visual C++ program?
• QA: Why does MFC adds "WCE_" prefix to my classes?
  January 14, 2003. I created a window of my custom class using MFC and noticed that the class name of the window got "WCE_" prefix. Why was it added? How can I get rid of it?
• QA: How can I handle command line parameters in MFC based application?
  March 21, 2002. I want to handle command line parameters in my MFC based application. The problem is that MFC based programs have only one copy and when I start my program and it's already running I cannot handle the command like parameters. Let's say instance A of my program is already running. I start instance B with some command line parameters. Instance B checks that instance A is running, sends A foreground and exits. So I cannot access command line parameters of B from instance A.
• QA: How to fix when the class wizard says Parsing error: Expected "afx_msg".?
  January 02, 2002. I have just created a new application using "WCE Pocket PC MFC AppWizard (exe)" template, opened the class wizard and got the following error message: 'Parsing error: Expected "afx_msg".'. How can I fix it?

MSDN Technical Articles

• One Source Code for Different Platforms
  If you are targeting more than one Windows CE platform, but you still want to maintain a single source code, then you can either choose to develop against the least common denominator or work with #ifdef $(CePlatform) preprocessor define. This article will show you how to use this define most effectively.
• Avoiding Common Memory Problems in C++
  For all of its power, C++ still has many of the inherent potential memory problems as C. In exchange for the raw speed and unrestricted access to memory provided for the language, you give up the protection offered by languages such as Visual Basic. Through consistent use of the techniques described in this article, you can help minimize the number of bugs that make it out of your development cycle into your end users' hands. While the techniques described are not unique to the Pocket PC, they will certainly help developers in their efforts to make Pocket PC applications (and thereby the Pocket PC itself) as reliable as possible.
• Advanced MFC Applications for the Pocket PC
  Developers can use Microsoft Foundation Classes (MFC) in a variety of ways. This article focuses on some of the more advanced topics of MFC and, as such, is targeted at developers who are familiar with basic MFC and C++ concepts.
• eMbedded Visual C++ 3.0
  Jan. 1, 2001. Microsoft has given developers the tools they need to create any application they can imagine. The keyword here is "given."

MS Knowledge base

• Third Function Argument Is Corrupted in Binaries Generated by ARM and THUMB Compilers
  10/16/2002. When you call a virtual function that resides in a different module, the third function argument may become corrupted.
• /Oxs Is Always Present in Project Options
  10/16/2002. When you change the C/C++ Optimizations Project setting, the compiler flags may not be affected as you expect. Instead, /Oxs is always present in project options regardless of the optimization you select.
• eVC Stops Responding When Doing Command-Line Build
  10/16/2002. When using the command-line build through eVC.exe, the program may stop responding.
• Error CBE6051 Internal Compiler" Error Message When You Are Using the SH Compiler for Windows CE 3.0
  10/30/2001. You may see the following error message when you are using the compiler for the SH processor for Windows CE 3.0: test.cpp(111) : error CBE6051: Internal Compiler Error (0xc0000005)
• BUG: eMbedded Visual C++ Always Displays CPU Mismatch Warning
  10/11/2001. Microsoft eMbedded Visual C++ displays a warning message that the CPU of the selected target does not match that of the remote Windows CE device connected to the Windows 2000 (Service Pack 1 or later) or Windows XP development host. For example, when the user clicks Go from the Build Debug menu while targeting a Pocket PC with an SH3 CPU, the following error message may appear: CPU Mismatch Warning, The CPU does not support configuration SH3! Executable will not run on device. Continue?
• BUG: Platform SDK Files Necessary to Rebuild MFC Libraries Missing
  6/12/2001. The Windows CE Platform SDK includes source code for Microsoft Foundation Classes (MFC), but may not include the makefile or definition files necessary for rebuilding these libraries
• Q215382 - BUG: "Type Mismatch" Error When You Call an eVC DLL That Returns Variants
  5/26/2001. When you try to call an eMbedded Visual C++ (eVC) dynamic-link library (DLL) that returns a variant, you receive a "Type Mismatch" error.
• Q265721 - DOC: /CEConfig Switch Builds Incorrect Platform
  5/10/2001. When you use the products listed above to build a project from the command line, the /CEConfig= switch is used to select the target platform. This switch is case sensitive and is followed by an equal sign (=). The online documentation incorrectly implies that the switch is case insensitive and does not contain an equal sign (CEConfig).
• Q266240 - PRB: Custom SDK Not Available for Existing eVC Projects
  5/10/2001. After you install a custom Software Development Kit (SDK) that was exported by Platform Builder 2.12 or later, you may not be able to select the new platform in the eMbedded Visual C++ IDE for any existing projects.
• Q266243 - HOWTO: Add CPU Support for Existing eVC Projects
  5/10/2001. When you develop applications for Windows CE devices, it may be necessary to later add support for another central processing unit (CPU) when you port an application to target a different type of device. This article explains how to use the eMbedded Visual C++ IDE to add CPU support for existing projects.
• Q298902 - BUG: Error CBE6052 Occurs While Compiling Windows CE Programs with Win32 Exception Handling
  6/13/2001. Code that includes a premature exit statement to exit from a __try block may fail to compile.

Questions and Answers at www.cegadgets.com

• Can I use C++ exceptions in my Windows CE application?
  27-Mar-01.
• Can I use STL in my Windows CE application?
  27-Mar-01.
• How does compiler optimization affect Windows CE executables?
  27-Mar-01.

CodeProject

• A Date and Time formatter
  7 Feb 2003. This class formats into strings COleDateTime objects. It uses the commonly defined formatting options such as MM-dd-yy or hh:mm:ss.

Libraries

• STL for Windows CE
  C++ library. It's known that eVC doesn't support exceptions and STL uses exceptions in almost all functions. This library adapts STL for Windows CE where eliminated all features which are not supported by the OS and/or by Microsoft's runtime library. In some cases Windows CE version of the missing functions are added - i.e. assert, abort, etc.
• Dinkum Abridged
  C++ library. The Dinkum Abridged Library for Windows CE has been in the field for several years. It includes our Standard C library, plus our Embedded C++ library, plus the Standard Template Library.