This article describes an issue that occurs when you create a Visual C++ Win32 console application in Windows Embedded Compact 2013. An update is available to resolve this issue. Before you install this update, all previously issued updates for this product must be installed.
Symptoms
When you create a Visual C++ Win32 console application by using Application Builder in Microsoft Visual Studio 2013, UNICODE is not defined in the newly created project. Example code are as follows:
int wmain(int argc, wchar_t *argv[])
{ printf("Welcome to Windows Embedded Project System \n"); #ifdef UNICODE printf("UNICODE is defined. \n"); #else printf("UNICODE is NOT defined. \n"); #endif printf("Please inster a char to end this app."); int c = getchar(); return 0; }
Resolution
Download information
Windows Embedded Compact 2013 Monthly Update (March 2015) is now available from Microsoft. To download this Windows Embedded Compact 2013 monthly update, go to Microsoft OEM Online or MyOEM.
More Information
Restart requirement
After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
-
On the Build menu, click Clean Solution, and then click Build Solution.
-
On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this software update.
Update replacement information
This update does not replace any other updates.
The English version of this software update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Files that are included in this hotfix package
File name |
File size |
Date |
Time |
Path |
---|---|---|---|---|
Stdafx.h |
716 |
02-Feb-2015 |
10:05 |
Public\Common\Sdk\Vstemplates\Vc\Windows embedded compact\Sdk_name\1033\Atldll |
Stdafx.h |
887 |
02-Feb-2015 |
10:05 |
Public\Common\Sdk\Vstemplates\Vc\Windows embedded compact\Sdk_name\1033\Application |
Stdafx.h |
716 |
02-Feb-2015 |
10:05 |
Public\Common\Sdk\Vstemplates\Vc\Windows embedded compact\Sdk_name\1033\Atlapplication |
Stdafx.h |
841 |
02-Feb-2015 |
10:05 |
Public\Common\Sdk\Vstemplates\Vc\Windows embedded compact\Sdk_name\1033\Dll |
Stdafx.h |
484 |
02-Feb-2015 |
10:05 |
Public\Common\Sdk\Vstemplates\Vc\Windows embedded compact\Sdk_name\1033\Consoleapplication |
Stdafx.h |
1,070 |
02-Feb-2015 |
10:05 |
Public\Common\Sdk\Vstemplates\Vc\Windows embedded compact\Sdk_name\1033\Mfcdll |
Stdafx.h |
1,596 |
02-Feb-2015 |
10:05 |
Public\Common\Sdk\Vstemplates\Vc\Windows embedded compact\Sdk_name\1033\Mfcactivexcontrol |
Stdafx.h |
1,331 |
02-Feb-2015 |
10:05 |
Public\Common\Sdk\Vstemplates\Vc\Windows embedded compact\Sdk_name\1033\Mfcapplication |
Stdafx.h |
789 |
02-Feb-2015 |
10:05 |
Public\Common\Sdk\Vstemplates\Vc\Windows embedded compact\Sdk_name\1033\Staticlibrary |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about software update terminology, see Description of the standard terminology that is used to describe Microsoft software updates.