Quantcast
Channel: Visual C forum
Viewing all 15302 articles
Browse latest View live
↧

Could not compile Wrapper C++/CLI project

March 3, 2020, 6:08 am
$
0
0

Hi,

I am working on a C++/CLI project which generates dll to be used in .net project. The CLI project also uses dll from unmanaged C++. I added import library (.lib) from unmanaged C++, but it fails with following log. I am out of ideas what is going wrong.

1>------ Build started: Project: Wrapper, Configuration: Debug x64 ------
1>Comp.cpp
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(104,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(104,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(105,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(105,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(106,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(106,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(121,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(121,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(122,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(122,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(123,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\minwinbase.h(123,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(51,24): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(51,24): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(52,24): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(52,24): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(172,24): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(172,24): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(584,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(584,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(585,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(585,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(586,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(586,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(637,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(637,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(638,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(638,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(639,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(639,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(964,24): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(964,24): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(1163,28): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(1163,28): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(1164,28): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(1164,28): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(1165,28): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapi.h(1165,28): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winbase.h(2377,26): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winbase.h(2377,26): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\timezoneapi.h(84,24): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\timezoneapi.h(84,24): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\timezoneapi.h(224,24): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\timezoneapi.h(224,24): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\timezoneapi.h(236,19): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\timezoneapi.h(236,19): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\rpcasync.h(291,18): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\rpcasync.h(291,18): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\shellapi.h(1611,132): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\shellapi.h(1611,132): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\shellapi.h(1612,133): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\shellapi.h(1612,133): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2328,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2328,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2329,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2329,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2368,25): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2368,25): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2383,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2383,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2384,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2384,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2494,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2494,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2495,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(2495,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(3895,25): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(3895,25): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(3896,25): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(3896,25): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(5284,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(5284,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(5673,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(5673,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(5691,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(5691,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(5692,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(5692,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(5712,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(5712,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(6924,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(6924,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(7000,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(7000,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(7792,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(7792,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(7823,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(7823,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17364,21): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17364,21): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17365,21): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17365,21): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17366,21): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17366,21): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17392,21): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17392,21): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17408,21): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17408,21): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17431,41): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(17431,41): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(21358,33): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\wincrypt.h(21358,33): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(712,15): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(712,15): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(731,15): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(731,15): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(775,16): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(775,16): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(787,16): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(787,16): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(802,16): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(802,16): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(814,16): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(814,16): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(3558,22): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(3558,22): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(3565,22): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(3565,22): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(3607,38): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(3607,38): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(3617,38): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\winspool.h(3617,38): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2218,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2218,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2219,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2219,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2220,14): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2220,14): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2296,44): error C2872: 'STATSTG': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2226,8): message : could be 'tagSTATSTG STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2296,44): message : or       'System::Runtime::InteropServices::STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\combaseapi.h(1465,25): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\combaseapi.h(1465,25): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(8520,29): error C2872: 'BIND_OPTS': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(8436,7): message : could be 'tagBIND_OPTS BIND_OPTS'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(8520,29): message : or       'System::Runtime::InteropServices::BIND_OPTS'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(8524,32): error C2872: 'BIND_OPTS': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(8436,7): message : could be 'tagBIND_OPTS BIND_OPTS'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(8524,32): message : or       'System::Runtime::InteropServices::BIND_OPTS'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(9007,43): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(9007,43): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(9011,45): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(9011,45): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(9430,45): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(9430,45): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(9845,58): error C2872: 'STATSTG': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2226,8): message : could be 'tagSTATSTG STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(9845,58): message : or       'System::Runtime::InteropServices::STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(9942,89): error C2872: 'STATSTG': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2226,8): message : could be 'tagSTATSTG STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(9942,89): message : or       'System::Runtime::InteropServices::STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(10058,61): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(10058,61): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(10059,61): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(10059,61): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(10060,61): error C2872: 'FILETIME': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared\minwindef.h(274,3): message : could be '_FILETIME FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(10060,61): message : or       'System::Runtime::InteropServices::FILETIME'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(10070,44): error C2872: 'STATSTG': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2226,8): message : could be 'tagSTATSTG STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(10070,44): message : or       'System::Runtime::InteropServices::STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(10665,44): error C2872: 'STATSTG': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2226,8): message : could be 'tagSTATSTG STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(10665,44): message : or       'System::Runtime::InteropServices::STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(14712,21): error C2872: 'BIND_OPTS': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(8436,7): message : could be 'tagBIND_OPTS BIND_OPTS'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(14712,21): message : or       'System::Runtime::InteropServices::BIND_OPTS'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(14722,24): error C2872: 'BIND_OPTS': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(8436,7): message : could be 'tagBIND_OPTS BIND_OPTS'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(14722,24): message : or       'System::Runtime::InteropServices::BIND_OPTS'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(14793,50): error C2872: 'STATSTG': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2226,8): message : could be 'tagSTATSTG STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(14793,50): message : or       'System::Runtime::InteropServices::STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(14801,89): error C2872: 'STATSTG': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidlbase.h(2226,8): message : could be 'tagSTATSTG STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\objidl.h(14801,89): message : or       'System::Runtime::InteropServices::STATSTG'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(657,14): error C2872: 'TYPEDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(653,8): message : could be 'tagTYPEDESC TYPEDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(657,14): message : or       'System::Runtime::InteropServices::TYPEDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(724,14): error C2872: 'TYPEDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(653,8): message : could be 'tagTYPEDESC TYPEDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(724,14): message : or       'System::Runtime::InteropServices::TYPEDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(726,17): error C2872: 'IDLDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(698,8): message : could be 'tagIDLDESC IDLDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(726,17): message : or       'System::Runtime::InteropServices::IDLDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(727,19): error C2872: 'PARAMDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(674,8): message : could be 'tagPARAMDESC PARAMDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(727,19): message : or       'System::Runtime::InteropServices::PARAMDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(742,14): error C2872: 'TYPEKIND': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(641,8): message : could be 'tagTYPEKIND TYPEKIND'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(742,14): message : or       'System::Runtime::InteropServices::TYPEKIND'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(751,14): error C2872: 'TYPEDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(653,8): message : could be 'tagTYPEDESC TYPEDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(751,14): message : or       'System::Runtime::InteropServices::TYPEDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(752,13): error C2872: 'IDLDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(698,8): message : could be 'tagIDLDESC IDLDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(752,13): message : or       'System::Runtime::InteropServices::IDLDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(837,30): error C2872: 'ELEMDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(729,3): message : could be 'tagELEMDESC ELEMDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(837,30): message : or       'System::Runtime::InteropServices::ELEMDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(838,14): error C2872: 'FUNCKIND': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(822,8): message : could be 'tagFUNCKIND FUNCKIND'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(838,14): message : or       'System::Runtime::InteropServices::FUNCKIND'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(839,16): error C2872: 'INVOKEKIND': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(831,8): message : could be 'tagINVOKEKIND INVOKEKIND'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(839,16): message : or       'System::Runtime::InteropServices::INVOKEKIND'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(840,14): error C2872: 'CALLCONV': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(812,8): message : could be 'tagCALLCONV CALLCONV'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(840,14): message : or       'System::Runtime::InteropServices::CALLCONV'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(845,14): error C2872: 'ELEMDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(729,3): message : could be 'tagELEMDESC ELEMDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(845,14): message : or       'System::Runtime::InteropServices::ELEMDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(877,14): error C2872: 'ELEMDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(729,3): message : could be 'tagELEMDESC ELEMDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(877,14): message : or       'System::Runtime::InteropServices::ELEMDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1021,33): error C2872: 'FUNCDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(847,8): message : could be 'tagFUNCDESC FUNCDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1021,33): message : or       'System::Runtime::InteropServices::FUNCDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1040,32): error C2872: 'VARDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(880,8): message : could be 'tagVARDESC VARDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1040,32): message : or       'System::Runtime::InteropServices::VARDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1054,33): error C2872: 'TYPEDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(653,8): message : could be 'tagTYPEDESC TYPEDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1054,33): message : or       'System::Runtime::InteropServices::TYPEDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1087,32): error C2872: 'IDLDESC': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(698,8): message : could be 'tagIDLDESC IDLDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1087,32): message : or       'System::Runtime::InteropServices::IDLDESC'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1353,35): error C2872: 'INVOKEKIND': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(831,8): message : could be 'tagINVOKEKIND INVOKEKIND'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1353,35): message : or       'System::Runtime::InteropServices::INVOKEKIND'
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1785,33): error C2872: 'TYPEKIND': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\oaidl.h(1785,33): fatal error C1003: error count exceeds 100; stopping compilation
1>Generating Code...
1>Done building project "Wrapper.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========


↧
Search

Getting error with multibyte character code C++

March 3, 2020, 4:59 am
$
0
0
cannot get it to work with multi byte character set
its working fine with unicode
i tried but wasn't able to convert it to multibye
This is the error i am getting
Hide   Copy Code
DWORD dwResult = GetLogicalDriveStrings(MAX_PATH, text); // text = szLogicalDrives
on this line i am getting cannot convert from wchar_t* to LPSTR

UINT nDriveType = GetDriveType(szSingleDrive);
on this line i am getting cannot convert WCHAR to LPCSTR
this is the code below

Hide   Copy Code
DWORD dwResult = GetLogicalDriveStrings(MAX_PATH, text); // text = szLogicalDrives
on this line i am getting cannot convert from wchar_t* to LPSTR

UINT nDriveType = GetDriveType(szSingleDrive);
on this line i am getting cannot convert WCHAR to LPCSTR
↧
↧

How to create Console Applications by using pure C-Language

March 3, 2020, 4:19 am
$
0
0
I like to use Visual Studio 2019 Community for pure C-Programming on my Windows 10 PC. That ist allegedly possible by naming a source file xxx.c instead of xxx.cpp. But at the end the Microsoft Windows Security recognizes the produced xxx.exe as a Trojaner (Win32/Ludicrouz.Z).
Do I made something wrong - please inform me how I can program pure C-Progams (C99 or later) with Visual Studio 2019.
Thank you in advance.
↧

Issue Release Dispatch Blocking

March 3, 2020, 7:04 am
$
0
0
i have an MFC application connecting to ms access. sometimes the connection.close fails and is blocking the entire application. This issue is happening with 1909 windows version (and we never get this error with 1903 version)
↧

MFC requires C++ compilation (use a .cpp suffix)/ C-files in a MFC-project?

June 4, 2012, 6:44 am
$
0
0

Hi!

I working with a MFC project in VS2010, the project compiling and the program is working.

Now I will try to add this project to a solution where we already have about 20 old c project. I do this because it belongs with that solution and I also want to use some functions in some of these c-files.

I have included the c-file (massivecfunctions.c ), with the functions I want to use, in my project with the /Tc flag only on that file(rest of my MFC project I have /Tp). When compiling  with #include "stdafx.h" I getting this error:

Error1 error C1189: #error :  MFC requires C++ compilation (use a .cpp suffix)c:\program files (x86)\microsoft visual studio 10.0\vc\atlmfc\include\afx.h15

When compiling without #include "stdafx.h" and "Not Using Precompiled Headers" on that file(rest of my MFC project I have Create (/Yc)).  I get this error:

Error4 error LNK2019: unresolved external symbol "int __cdecl getint(int)" (?getint@@YAHH@Z) referenced in function "protected: __thiscall CStartupThrd::CStartupThrd(void)" (??0CStartupThrd@@IAE@XZ)C:\StartupThrd.obj

Is it possible to use C-files in a MFC-project? 

Regards

Whane


↧
↧

Very strange phenomenon: output file filled or truncated with binary zeros. What could cause that?

February 11, 2016, 5:33 am
$
0
0

Very strange phenomenon: output file filled or truncated with binary zeros

I have recently encountered a very strange phenomenon which I'm at a loss to account for.  I have had reports in the last few weeks from 4 users who say that they have lost data from the file that my application writes to.  I have been able to see two of the files.  One of them is about 34KB and viewed in a binary editor it contains nothing but binary zeros.  The other is about 40MB and if I view it in a binary editor, it is fine up to offset 02600000 (hex), but from 02600000 onwards it contains nothing but binary zeros.

I don't know for sure that all 4 have experienced the same thing, but it sounds as if 3 of them have had very similar truncation, and the 4th has lost everything.

The way my app saves is like this: the app writes to a temporary file.  If any error occurs, the save is aborted. If the save succeeds, the original file is deleted and the temporary file is renamed to replace it.  None of the users reported any problems when they saved.  The problem occurred the next time they tried to view their data.

I estimate the chance that this was caused by a bug in my code as approaching zero.  I am a very experienced coder and I have checked it meticulously and can find no way that my code could have done this.  The code uses CFile::Write to write to the file.  The truncated file actually split a keyword that was being written out.  Low-level buffering code might conceivably have done that, and my code does do its own buffering, but this part of the code has not been changed in over 10 years, and has behaved faultlessly throughout that time.  If an error did occur, I can think of no way that it would result in binary zeros being output.  Also, why do zeros start at hex 02600000?  Surely it can't be a coincidence that it starts at a round number that ends in 5 zeros?  But this is a round number only in hex terms, and my code doesn't use hex for buffer sizes (or any sizes). All sizes are specified in decimal values.

So I ask myself - Why after years of working fine have I had 4 reports like this in a window of less than 3 weeks? Why binary zeros?  Why in the truncation case I say did they start on a (hex) round number?

I have not been able to confirm that they're all using the same version of my software, but it looks like that.  That version has been around for just under a year.  Why problems now?  I only know the Windows versions for two of them.  One had Windows 7 and another had Windows 10.  One user said they hard recently run a defrag on their hard drive.  Could that be relevant?  An attempt to defrag an SSD maybe? (I don't know if they have SSDs).  A virus?  A weird new fault in a service patch, miraculously affecting both Windows 7 and Windows 10?

Any ideas anyone?

Simon

↧

Side by Side Configuration Is Incorrect Error in Windows 10

March 4, 2020, 5:41 am
$
0
0

Hi All,

After I installed special software I got message "Side by Side Configuration Is Incorrect Error"

Activation context generation failed for "C:\Program Files (x86)\Baker Hughes\MetaWin\MetaWin.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.6195" could not be found. Please use sxstrace.exe for detailed diagnosis.

This program was working fine just a few days before I re-install Win-10.

Thanks in advance for any support

↧

Internal linker error.

January 5, 2020, 4:01 pm
$
0
0

Visual Studio 2019 Community v. 16.4.2, MFC project with Win 10 SDK, MFC 142 and C++ 17 ISO. OS is Win 10 Home.

The project was moved from machine with Win 7 Pro SP1. Under Win 7 the project was build and run in Debug and Release x96 configurations without problem. On new machine with Win 10 Home the Debug x86 configuration works fin, but Release x85 issues fatal linker error:

1>Generating code
1>LINK : fatal error C1001: An internal error has occurred in the compiler.
1>(compiler file 'd:\agent\_work\6\s\src\vctools\Compiler\Utc\src\p2\main.c', line 166)
1> To work around this problem, try simplifying or changing the program near the locations listed above.
1>Please choose the Technical Support command on the Visual C++
1> Help menu, or open the Technical Support help file for more information
1>  link!InvokeCompilerPass()+0x2e4f2
1>  link!InvokeCompilerPass()+0x21ee0
1>  link!InvokeCompilerPass()+0x21e01
1>  link!InvokeCompilerPass()+0x2d584
1>
1>LINK : fatal error C1001: An internal error has occurred in the compiler.
1>(compiler file 'd:\agent\_work\6\s\src\vctools\Compiler\Utc\src\p2\main.c', line 166)
1> To work around this problem, try simplifying or changing the program near the locations listed above.
1>Please choose the Technical Support command on the Visual C++
1> Help menu, or open the Technical Support help file for more information
1>  link!InvokeCompilerPass()+0x2e4f2
1>  link!InvokeCompilerPass()+0x21ee0
1>  link!InvokeCompilerPass()+0x21e01
1>  link!InvokeCompilerPass()+0x2d584
1>
1>
1>LINK : fatal error LNK1000: Internal error during IMAGE::BuildImage
1>
1>  Version 14.24.28314.0
1>
1>  ExceptionCode            = C0000005
1>  ExceptionFlags           = 00000000
1>  ExceptionAddress         = 79B93EAE (796D0000) "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\bin\HostX86\x86\c2.dll"
1>  NumberParameters         = 00000002
1>  ExceptionInformation[ 0] = 00000000
1>  ExceptionInformation[ 1] = 00000000
1>
1>CONTEXT:
1>  Eax    = 00000000  Esp    = 007CE638
1>  Ebx    = 00000000  Ebp    = 007CE648
1>  Ecx    = 00001505  Esi    = 00000000
1>  Edx    = 00000000  Edi    = 00000000
1>  Eip    = 79B93EAE  EFlags = 00010246
1>  SegCs  = 00000023  SegDs  = 0000002B
1>  SegSs  = 0000002B  SegEs  = 0000002B
1>  SegFs  = 00000053  SegGs  = 0000002B
1>  Dr0    = 00000000  Dr3    = 00000000
1>  Dr1    = 00000000  Dr6    = 00000000
1>  Dr2    = 00000000  Dr7    = 00000000
1>Done building project "ANNet.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

I did not find VS 2019 in the list of MS Appa it Tech Support so I am using this forum. 

Againm debug conf works without complaints.

What to do?

↧
Search

how to convert printf dword in a loop into a string in c++

March 4, 2020, 8:44 pm
$
0
0

below is the code which is producing a md5 hash but its printing it and i want to store it in a char array or more preferably in a string

for (DWORD i = 0; i < cbHash; i++)
{
printf("%c%c", rgbDigits[rgbHash[i] >> 4],
rgbDigits[rgbHash[i] & 0xf]);
}

//rgbHash is of BYTE type

//rgbDigits is of CHAR type

how can i store above printf() value in a string?


↧
↧

High DPI MFC Application text string Cut off

March 4, 2020, 9:48 pm
$
0
0

reference to: https://devblogs.microsoft.com/cppblog/mfc-applications-now-default-to-being-dpi-aware/

MFC applications now defaut to being DPI-aware , but it also exists that text string are cutted off in hight dpi ,specially in 125dpi

the following code is the rc in vs2017：

IDD_DPITEST_DIALOG DIALOGEX 0, 0, 265, 58
STYLE DS_SETFONT | DS_FIXEDSYS | WS_POPUP | WS_VISIBLE | WS_CAPTION | WS_SYSMENU | WS_THICKFRAME
EXSTYLE WS_EX_APPWINDOW
CAPTION "dpiTest"
FONT 8, "MS Shell Dlg", 0, 0, 0x1
BEGIN
    LTEXT           "",IDC_STATIC,96,24,9,9,SS_NOTIFY
    LTEXT           "",IDC_STATIC,89,10,9,9,SS_NOTIFY
    CONTROL         "Te&xt-based document",IDC_STATIC,"Button",BS_AUTORADIOBUTTON | WS_GROUP,6,10,81,10
    CONTROL         "&Image-based document",IDC_STATIC,"Button",BS_AUTORADIOBUTTON,6,23,85,10
    DEFPUSHBUTTON   "OK",IDOK,209,37,50,14
    PUSHBUTTON      "Cancel",IDCANCEL,208,37,50,14
END

it is normal in 100 or 150 dpi  in my pc

but it is cutted off in 125 or 175 dpi in vs2017

The solution I can think of  is to widen the corresponding truncated control resources

Is there any other solution to solve it completely?



↧

How to get only the single char in char*

March 4, 2020, 10:20 pm
$
0
0

i have a char* in which i wan to store only a single char coming from a char named NEW_DRIVE_LIST

now issue is that with below mentioned way i am getting correct first element from NEW_DRIVE_LIST but its also adding extra 

0000 after the value of NEW_DRIVE_LIST

char *b ;
  b = &NEW_DRIVE_LIST[i];

what i want is this

char NEW_DRIVE_LIST='C';

char *b=NEW_DRIVE_LIST[i]+":";

SO THAT i get b="C:" and not the extra garbage value

↧

Function call doesn't work second time

March 5, 2020, 6:52 am
$
0
0

i made a code its very messy and perfect example of  a dirty code but it is what it is.

whats its supposed to do is to scan usb files whenever usb is inserted but the issue is that on second call its not working

i mean when program is ran first time it works fine but whenever i remove and insert usb again it doesnt scan files

i have set some flags so that when usb is removed and connected again then it calls the function (getfil) again but its not working i have spent hours on trying to fix it but i am unable to do that so i am posting the code below:-

if ((NEW_DRIVE_LIST[i] >= 65 && NEW_DRIVE_LIST[i] <= 89) && (PREV_DRIVE_LIST[i] == '0')) {

printf("\nNew Device Inserted%d : %c", count++, NEW_DRIVE_LIST[i]);

st+= NEW_DRIVE_LIST[i];
PREV_DRIVE_LIST[i] = NEW_DRIVE_LIST[i];

me++;


}
if (me > 1)
{
//cout << st;
while (flag != false)
{
k = sizeof(st);
for (int i = 0; st[i] <= 'Z';)
{
ch2[i] = st[i];
if (getfil((void*)ch2) != 1)
{
strcat(ch2, ":");
getfil((void*)ch2);//this is where the problem is it works fine for first time only
//cDriveLetter[i]++;
}
st[i]++;

}
flag = false;
}
break;

}

}

and below is the getfil function complete:-

int getfil(void *args)
{

string st;
while (getline(read, st))
{
if (st.size() > 0)
filen.push_back(st);
else
break;

}



char *tmpPath = (char *)args;
string sPath(tmpPath);
//sPath += ":";
WIN32_FIND_DATA FindFileData;
string sTmpPath = sPath;
sTmpPath += "\\*.*";

string currFile = "";

HANDLE hFind = FindFirstFile(sTmpPath.c_str(), &FindFileData);
if (hFind == INVALID_HANDLE_VALUE) {
//cout << "Not a valid path\n";
return 0;
}
else
{
do
{
//check if its a directory...
if ((FindFileData.dwFileAttributes & FILE_ATTRIBUTE_DIRECTORY))
{
string filePath = FindFileData.cFileName;
//ignore '.' and '..'
if (strcmp(".", filePath.c_str()) && strcmp("..", filePath.c_str()))
{

//Dont list recycle bin content...
if (filePath == "$RECYCLE.BIN" || filePath == "$Recycle.Bin")
continue;
sTmpPath = sPath + "\\" + filePath;
getfil((void *)sTmpPath.c_str());
}
}
else                       //its a file...
{
sTmpPath = sPath + "\\";
currFile = sTmpPath + FindFileData.cFileName;
TCHAR curfil[1024];
_tcscpy_s(curfil, CA2T(currFile.c_str()));
string ext = PathFindExtension(curfil);
//const char ex = ext;
if (/*strcmp(ext.c_str(), ".txt") == 0||*/ strcmp(ext.c_str(), ".doc") == 0 ||
strcmp(ext.c_str(), ".docx") == 0 || strcmp(ext.c_str(), ".pdf") == 0 ||
strcmp(ext.c_str(), ".xlx") == 0 || strcmp(ext.c_str(), ".xlsx") == 0 ||
strcmp(ext.c_str(), ".ppt") == 0 || strcmp(ext.c_str(), ".pptx") == 0)
{

string str;
bool toWrite = true;

for (vector<string>::iterator t = filen.begin(); t != filen.end(); t++)
{
int i = 0;
//string s = t.c_str();
if (t[i] == currFile)
{
toWrite = false;
i++;
}

}

if (toWrite == true)
{
//file.open("UsbScannedFiles.txt",ios::app);
file << /*counter << "-" <<*/ currFile << endl;
//string k = FindMd5(curfil);
FindMd5(curfil);
//file << FindMd5(curfil)<<endl;
counter++;
}
}
else {

}
}
} while (FindNextFile(hFind, &FindFileData) != 0);

//read.close();
FindClose(hFind);

}
return 1;
//flag = false;
//return 0;
}

↧

S-BOX ENCRYPTION

March 5, 2020, 9:18 am
$
0
0

HI 

how can i do an encryption algorithm with sbox?it's in c++.

my algorithm is :C = k[1] ⊕ Sbox(P ⊕ k[0])

where c is the cipher text, p is the plain text and the key is two characters 

help me please :(

↧
↧

Separate char * 1000 with a certain size number

March 5, 2020, 10:28 am
$
0
0 
char str[1000] = "This#is#a#sample#string";
  pch=strchr(str,'#');
  while (pch!=NULL)
  {
    printf ("%s\n",str);

    int NewTop = 10;

    pch=strchr(NULL,'#');
  }

I need help

according to this code it is to add spaces to a character,

what I want is to do something similar but in this case I want to separate

a text in parts according to the size of the text

example of the char 5 text and print it

example:

This# : size 5
is#a# : size 5
sampl : size 5
e#str : size 5
ing : size 5 or less

↧

How to compare two files line by line after storing them in vector

February 28, 2020, 10:47 am
$
0
0 
i have two text files named totalfiles.txt and uploaded.txt i am storing both of them in a vector now offcourse when this program will run for a very first time uploaded.txt will be made and it will be empty and first file will be written in it after its successfully uploaded to the server what i want is some kind of method to compare both .txt files so if files that are already uploaded to server don't get uploaded again so is there any method to do that in c++? again at the beginning i am going to store the files in vector and i need to do above operation via vector and not using .txt files directly with fstream
ifstream read2("ScannedFiles.txt");
ofstream read3("Problem.txt", ios::app);
fstream uploaded("Uploaded.txt", ios::app);
vector<string>filen2;
vector<string>upl;
string st3;
string st2;
while (getline(read2, st2))
{
if (st2.size() > 0)
filen2.push_back(st2);
else
break;

}
while (getline(uploaded,st3))
{
if (st3.size() > 0)
upl.push_back(st3);
else
break;
}
<pre>for (vector<string>::iterator t = filen2.begin(); t != filen2.end(); t++)
↧
Search

AfxGetMainWnd() returns NULL

March 6, 2020, 12:40 am
$
0
0

Hi,

My application is MFC MDI application.

int CMainFrame::OnCreate(LPCREATESTRUCT lpCreateStruct)
{
if (CMDIFrameWndEx::OnCreate(lpCreateStruct) == -1)
return -1;

CMainFrame* pFrame = (CMainFrame*)AfxGetMainWnd();
}

Why AfxGetMainWnd() returns NULL in my application

↧

std::make_signed is not coherent with gcc and clang

March 6, 2020, 1:53 am
$
0
0

Hi,

On Visual Studio 2019 v142 ( The latest version, I don't no tried oldest but I think the problem is the same )

The following code do not give the same result as GCC or Clang:

enum class B : char;
std::make_signed_t<B> // This gives int on visual studio but signed char on GCC and Clang.

So who is right? char is the smallest integral type that represent the enumeration. I think Visual Studio is wrong and this make code dangerous if you expect ‘signed char’ and not ‘signed int’.

Thank you,


↧
↧

DLL Missing MSVCP140D With registry Key

March 6, 2020, 5:39 am
$
0
0

Hy

I have build a application  with visual studio 2019 and MFC . I write a key to lunch automaticly my application at users start

"Software\\Microsoft\\Windows\\CurrentVersion\\Run". It's ok. When users start the application try to start and i have the message "File missing MSVCP140D.dll". So i have modified my program to see where i lunch my application. I found "c:\windows\system32". So MSVCP140D it's not in "c:\windows\system32". I don't know how solved this problem. Do have an idea?

Thanks

Jean Bezet

↧

map not initialised properly, Pnode is null

June 8, 2014, 2:17 pm
$
0
0

I have this code:

std::map<string,fType> FileMap::fTypeMap;

void FileMap::setTypes()
{

  // project file 
  fTypeMap["FIDX"] = FIDX;

// etc

}

(fType is an enum)

This line crashes at runtime with an exception. If I step through the insert call I encounter the following:

mapped_type& operator[](key_type&& _Keyval)
{// find element matching _Keyval or insert with default mapped
iterator _Where = this->lower_bound(_Keyval);

iterator lower_bound(const key_type& _Keyval)
{// find leftmost node not less than _Keyval in mutable tree
return (iterator(_Lbound(_Keyval), this));
}

_Nodeptr _Lbound(const key_type& _Keyval)
{// find leftmost node not less than _Keyval
_Nodeptr _Pnode = _Root();
_Nodeptr _Wherenode = this->_Myhead;// end() if search fails

_Nodeptr& _Root() const
{// return root of nonmutable tree
return (this->_Parent(this->_Myhead));
}

This returns 0.

I don't understand this. The tree for the map seems not to have been set up. I don't see any tests to see whether the tree needs to be initialised. 

This seems like a simple insertion. Why doesn't it work? Is it anything to do with the fact that the declaration is static and some constructor has not been called?

I'm baffled.

↧

One block of memory with two pointers for two different processes in unmanaged situation?

March 6, 2020, 12:39 pm
$
0
0

I have a problem of transferring some integer values that are generated at a fast clip in MFCaptureD3D. The latter is a GitHub project that captures pixel values of standard WebCam. It is a C++ application. A few variants have been considered, including named pipes and named shared memory. They still might be used but analyzing the code I noticed that there is considerable overhead in each method and that I am afraid will make them impractically slow and chocked with the data. So I want to define one block of memory with the stipulation that I could also define two pointers attached to it. I think I can use one of them to write the data and the other one to read. My question is are there any pitfalls in the idea? If there are I will abandon it and try to do named pipes.

int* ptr1[76800];

So, how do I define the second pointer if it is at all possible?    process A, writer ==> [memory] ==> process B, reader.

Thanks, -MyCatAlex


↧
Viewing all 15302 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>