You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2019. It is now read-only.
I have Visual Studio 2012 Professional and used it for years without a problem.
Then some day I needed Visual Studio 2015, installed it, then uninstalled main app only using standard uninstaller via Control Panel -> Add/Remove Programs. My OS is Windows 7 SP1.
Some day I needed to compile Webkit and it's vswhere.exe found Visual Studio 2015 and build failed.
I thought I need clean uninstall Visual Studio 2015 but don't know how and have no installer and no idea why vswhere.exe detected it. So I tried this "Visual Studio Uninstaller". It found some leftovers from VIsual Studio 2015, and removed them successfully.
I rebooted a PC and tried to run Visual Studio 2012. It failed to run. I ran repair using Visual Studio 2012 installer, it ran but now I cannot compile 32-bit executables.
Every time I trying to build for Win32_x86 cl.exe fails with ">C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB6006: "CL.exe" はコード -1073741701 を伴って終了しました。".
I tried reinstall Visual Studio 2012, with or without update 5, clean reinstall multiple times, including reinstall of .NET Framework all versions, still the same problem. Win32 AMD64 compiler works without problem. Also I tried to replace C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\cl.exe by dummy 32-bit exe which does nothing, but still have 0xc000007b error when it runs.
When I run Visual Studio command line tools batch, both 32-bit and 64-bit cl.exe are work perfectly fine inside it: run, compile sources, compiled binary runs fine.
I have an error above only when cl.exe (32-bit x86) ran from Visual Studio 2012 IDE. Not sure what's wrong, but if anyone knows a workaround WITHOUT reinstall OS, please give it to me. Thanks!
The text was updated successfully, but these errors were encountered:
@noangel there is a huge warning on this tools home page that indicates "WARNING: running this application may stop earlier remaining installations of Visual Studio 2012 and earlier from working, because Visual Studio 2012 and below share MSI upgrade code with Visual Studio 2013 and above."
I have Visual Studio 2012 Professional and used it for years without a problem.
Then some day I needed Visual Studio 2015, installed it, then uninstalled main app only using standard uninstaller via Control Panel -> Add/Remove Programs. My OS is Windows 7 SP1.
Some day I needed to compile Webkit and it's vswhere.exe found Visual Studio 2015 and build failed.
I thought I need clean uninstall Visual Studio 2015 but don't know how and have no installer and no idea why vswhere.exe detected it. So I tried this "Visual Studio Uninstaller". It found some leftovers from VIsual Studio 2015, and removed them successfully.
I rebooted a PC and tried to run Visual Studio 2012. It failed to run. I ran repair using Visual Studio 2012 installer, it ran but now I cannot compile 32-bit executables.
Every time I trying to build for Win32_x86 cl.exe fails with ">C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB6006: "CL.exe" はコード -1073741701 を伴って終了しました。".
I tried reinstall Visual Studio 2012, with or without update 5, clean reinstall multiple times, including reinstall of .NET Framework all versions, still the same problem. Win32 AMD64 compiler works without problem. Also I tried to replace C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\cl.exe by dummy 32-bit exe which does nothing, but still have 0xc000007b error when it runs.
When I run Visual Studio command line tools batch, both 32-bit and 64-bit cl.exe are work perfectly fine inside it: run, compile sources, compiled binary runs fine.
I have an error above only when cl.exe (32-bit x86) ran from Visual Studio 2012 IDE. Not sure what's wrong, but if anyone knows a workaround WITHOUT reinstall OS, please give it to me. Thanks!
The text was updated successfully, but these errors were encountered: