Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, April 8, 2017 11:15 AM
I recently learnt to develop a plug-in of a sound analysis platform by using cpp. But the given pre-compiled libraries was complied by a previous compiler whose MSC_VER is 1800 and it may lead to LINK 2038 error when I try to build it. Then I tried to find a way to install the platform toolset with version v120 but I can only find v140 (VS2015) in the Visual Studio installer. So is there any way to work this out? Many thanks.
All replies (3)
Monday, April 10, 2017 5:36 AM | 1 vote
Hi,
VS 2017 can use old toolsets as long as they are installed:
So for v120 you will need to install VC++ 2013, because Build Tools 2013 doesn't include C++:
http://stackoverflow.com/questions/19914828/microsoft-build-tools-2013-missing-v120-directory
My portal and blog about VSX: http://www.visualstudioextensibility.com; Twitter: https://twitter.com/VSExtensibility; MZ-Tools productivity extension for Visual Studio: https://www.mztools.com
Monday, April 10, 2017 9:09 AM
Hi cocoaVan,
Welcome to the MSDN forum.
Refer to your description, if you want the platform toolset v120 for the C++ project in VS 2015 or VS 2017, you need to install the VS 2013 to work side by side.
Since your project is C++ type and please have a look at the following similar issues:
Installing Platform Toolset v120 under Visual Studio 2015
Is it possible to add the Visual C++ v120 Compiler Tool Set to Visual Studio 2015?
The old versions of VS can find from here: https://www.visualstudio.com/vs/older-downloads/
Best regards,
Sara
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].
Monday, April 17, 2017 6:02 AM | 1 vote
Hi cocoaVan,
Sorry to trouble you and have you tried Carlos's reply or mine? If you meet any other issues, please feel free to let me know.
If the reply is works for your issue, please mark it as answer and that will help other community members to search this useful information. Or if you solved this issue by yourself, could you please share your workaround in here when you have free time, thanks in advance.
Best regards,
Sara
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].