#pragma comment manifestDependency

  • Thread starter Thread starter Keith Hill MVP
  • Start date Start date
K

Keith Hill MVP

Guest
What is this goo used for? It is new in the July CTP:

#pragma comment(linker,"/manifestdependency:\"type='win32' " \
"name='" __LIBRARIES_ASSEMBLY_NAME_PREFIX ".CRT' " \
"version='" _CRT_ASSEMBLY_VERSION "' " \
"processorArchitecture='x86' " \
"publicKeyToken='" _VC_ASSEMBLY_PUBLICKEYTOKEN "'\"")

We have a special preprocessor that is generating a warning on this for just about every file we process. We get:

expected ')'; found identifier '__LIBRARIES_ASSEMBLY_NAME_PREFIX'

What happens if we remove this macro and it's debug cousin?

--
Keith

Continue reading...
 

Similar threads

B
common-controls version 6 not working when declared in dll in 64-bit version
Replies
0
Views
198
Bezhad
B
R
Extended CLIstBox control not receiving message to populate Context menu as part of Press and Hold operation in surfacePro device.
Replies
0
Views
95
ravinalla
R
R
Property page showing through
Replies
0
Views
109
rameshdk
R
H
Looking for compiler macro to skip #pragma comment(lib,"filename.lib")
Replies
0
Views
138
hector santos
H
V
C++ Common Controls to Visual Styles MFC Controls
Replies
0
Views
76
Volki69
V
Back
Top