R
rhfritz
Guest
I migrated to a new Win10 Enterprise computer. After a new install of VS2017 Pro (v15.4.3), building my solution (which builds fine on the 2107 install on the old computer), generates this error:
c:\program files (x86)\microsoft visual studio\2017\professional\vc\tools\msvc\14.11.25503\atlmfc\include\afx.h(62): fatal error C1083: Cannot open include file: 'new.h': No such file or directory
And there were many other of the "standard" libraries similarly flagged.
The solution file is comprised of a large number of c++ projects representing MFC DLL's, libs, and standalone exe's which use MBCS versus Unicode.
Running the "Repair" option from Visual Studio Installer did not fix it.
I think I've solved this before, and it has something to do with the SDK, but I can't remember what I did to fix it. Any guidance appreciated.
--------------------------------------------------------
Update: I resolved the issue by running the Visual Studio Installer on the working system and taking a screen snapshot of the options selected. When I made the options match on the new system, mostly this involved unchecking the box for Universal Windows Platform development, our code built. Unfortunately, it isn't obvious why this option is apparently the wrong option.
rhfritz
Continue reading...
c:\program files (x86)\microsoft visual studio\2017\professional\vc\tools\msvc\14.11.25503\atlmfc\include\afx.h(62): fatal error C1083: Cannot open include file: 'new.h': No such file or directory
And there were many other of the "standard" libraries similarly flagged.
The solution file is comprised of a large number of c++ projects representing MFC DLL's, libs, and standalone exe's which use MBCS versus Unicode.
Running the "Repair" option from Visual Studio Installer did not fix it.
I think I've solved this before, and it has something to do with the SDK, but I can't remember what I did to fix it. Any guidance appreciated.
--------------------------------------------------------
Update: I resolved the issue by running the Visual Studio Installer on the working system and taking a screen snapshot of the options selected. When I made the options match on the new system, mostly this involved unchecking the box for Universal Windows Platform development, our code built. Unfortunately, it isn't obvious why this option is apparently the wrong option.
rhfritz
Continue reading...