Atlwinverapi.h(712): error C3861: 'lcmapstringex': identifier not found

Question

1.44/5 (3 votes)

See more:

i am converting a vs 2008 project to vs2017.
plz help me how to solve this error.

What I have tried:

i tried of changing winver 0x0400 and _win32_winnt 0x0400 to 0x601.

Posted 30-Jul-17 21:42pm

Naveen_vemuri

Updated 12-Aug-17 5:24am

Add a Solution

Comments

Jochen Arndt 31-Jul-17 5:03am

Where did you defined them?

They must be defined before including any Windows header file. That is on top of stdafx.h with precompiled headers. Otherwise on top of each file that includes Windows header files or as global compiler option in the project settings.

If the error is then still there, there might be a re-definition in some of your files.

However, you should have seen the error with VS 2008 too with missing or wrong definitions.

How are you converting the project?
Did you use the VS 2008 project folder or a full copy?
If yes, delete all output and intermediate files or do a full rebuild.

Naveen_vemuri 31-Jul-17 7:58am

i am building project using MsBuild.I opened vs2008 project in vs2017 and it made the necessary changes to convert it to vcxproj.I am not aware of what was written in source files.I am rewriting batch file and setting required environment to build it without visual studio.There are nearly 20-30 cpp files and so many headerfiles in that project.there is one stdafx.h file but in that there is no windows.h file included.i made changes in the file above i mentioned(atlwinverapi.h) like i find the declaration of "LCMapStringEx" in WinNls.h file i just copied and pasted in this file and the error is resolved.but after i got another error afxwin.h file not found and i gave paths to the atl library.then this identifier not found error is again coming.i am not getting exact clarity of what to do to resolve this error.

Jochen Arndt 31-Jul-17 8:15am

If there is an stdafx.h file it is probably used.
The windows.h header file is included by other files from that header file.
When adding the definitions, they must be on top of the stdafx.h file.

As already mentioned below by Richard, default values are selected by VS when the definitions are not present. Then there should be no problems when updating to a newer VS version and newer SDK versions.

"I am rewriting batch file and setting required environment to build it without visual studio."

Try first to rebuild from within the VS 2017 IDE. That will overwrite old output files and ensures usage of the selected SDKs.

Once that is creating the target without errors, you can try to use your batch file and MSBuild.

Naveen_vemuri 1-Aug-17 1:17am

i added definitions on top of stdafx.h file.but the error is not resolved.what is the meaning of this error?why the error is coming in a headerfile provided by microsoft atl library file?

Jochen Arndt 1-Aug-17 3:05am

The function is defined in winnls.h which is included by windows.h.

The definition is guarded for the minimum target windows version (Vista).
This guard uses one of your definitions or NTDDI_VERSION (which is created from the other definition within sdkddkver.h).

So you have to check which definition is active when winnls.h is included. You might also follow the include file tree by enabling extended compiler output to show each file processed. Than you can step back from the error to check all non-MS files if there is a strange setting somewhere.

But only you can do that because it requires to have the full project. I have no VS 2017 installed here at work (only at home) so that I even can't check the VS 2017 SDK files.

Naveen_vemuri 3-Aug-17 7:12am

i tried removing those definitions and building by VS IDE2017.but still i am getting that error.

Jochen Arndt 3-Aug-17 7:21am

The definitions can be there if on top of stdafx.h before including any other file. If they are there, they are used (and does not harm provided they are correct).

You might then include sdkddkver.h. That will check the definitions and define NTDDI_VERSION accordingly.

Then the common MFC / ATL header files should be included.

If the error then still occurs, the problem is probably located somewhere in your source files. But only you have these files and can check them therefore.

As already mentioned, I don't have VS 2017 here. So you might have a look at the function declaration in winnls.h to check how it is guarded (WINVER, NTDDI_VERSION, or _WIN32_WINNT). You may also check if there is another guard using a different definition. Ensure that the conditions are met so that the function is declared.

Richard MacCutchan 31-Jul-17 7:18am

You should remove both those definitions and allow the compiler to find the default as defined in sdkddkver.h, which should select the latest one. Also check that your project settings have been updated to the latest SDK version (Project ->Settings->General).

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Member 13358397 · Accepted Answer · 2017-08-12T05:24:00

1. Search for definitions of _WIN32_WINNT in the current project files, if there are some of them, erase them.

2. Add StdAfx (header and source) files in the project.

3. In StdAfx.h define the following macros:

#define _WIN32_WINNT 0x0A00
#define _ATL_APARTMENT_THREADED
#define _USING_V110_SDK71_
#define _ATL_XP_TARGETING

4. Include StdAfx.h header to the source files that needs these macros. StdAfx.cpp is required to always include its header.
5. Insert the respective macros; go to the Project Properties, Configuration Properties, C/C++, Preprocessor, edit Preprocessor Definitions, and insert these macros with the next syntax:

NTDDI_VERSION= 0x06030000
WINVER=0x0A00
_WIN32_WINNT=0x0A00

6. Additionally, In StdAfx.h include the following “Afx” headers after the Macros definitions:

#define VC_EXTRALEAN // Exclude rarely-used stuff from Windows headers

#include <afxwin.h> // MFC core and standard components
#include <afxext.h> // MFC extensions

#ifndef _AFX_NO_OLE_SUPPORT
#include <afxole.h> // MFC OLE classes
#include <afxodlgs.h> // MFC OLE dialog classes
#include <afxdisp.h> // MFC Automation classes
#endif // _AFX_NO_OLE_SUPPORT

#ifndef _AFX_NO_DB_SUPPORT
#include <afxdb.h> // MFC ODBC database classes
#endif // _AFX_NO_DB_SUPPORT

#ifndef _AFX_NO_DAO_SUPPORT
#include <afxdao.h> // MFC DAO database classes
#endif // _AFX_NO_DAO_SUPPORT

#include <afxdtctl.h> // MFC support for Internet Explorer 4 Common Controls
#ifndef _AFX_NO_AFXCMN_SUPPORT
#include <afxcmn.h> // MFC support for Windows Common Controls
#endif // _AFX_NO_AFXCMN_SUPPORT

#include <windows.h>