Microsoft Visual C++#vc9

The predecessor to Visual C++ was called Microsoft C/C++. There was also a Microsoft QuickC 2.5 and a Microsoft QuickC for Windows 1.0. The Visual C++ compiler is still known as Microsoft C/C++ and as of the release of Visual C++ 2015 Update 2, is on version 14.0.23918.0.{{citation needed|date=May 2021}}

• {{anchor|c1}}Microsoft C 1.0, based on Lattice C, was Microsoft's first C product in 1983. It was not K&R C compliant.
• C 2.0 added large model support, allowing up to 1MiB for both the Code Segment and Data Segment.{{Cite book |url=http://archive.org/details/Computer_Language_Issue_06_1985-02_CL_Publications_US |title=Computer Language - Issue 06 (1985-02)(CL Publications)(US) |date=February 1985}}
• C 3.0 was the first version developed inside Microsoft.{{cite magazine |last=Leibson |first=Steve |date=1985-02-01 |title=Software Reviews: Expert team analyzes 21 C compilers |url=https://archive.org/details/Computer_Language_Issue_06_1985-02_CL_Publications_US/page/n85/mode/2up?q=microsoft+c+3.0 |magazine=Computer Language |access-date=2020-06-05 }} This version intended compatibility with K&R and the later ANSI standard. It was being used inside Microsoft (for Windows and Xenix development) in early 1984. It shipped as a product in 1985.
• C 4.0 added optimizations and CodeView, a source-level debugger.
• C 5.0 added loop optimizations and huge memory model (arrays bigger than 64 KB) support.
• C 5.1 released in 1988 allowed compiling programs for OS/2 1.x. The fourteen 5.25" disk (two of which were 1.2 MB, the others 360k) version included QuickC. The eleven 720k 3.5" disk version included with the OS/2 Software Development Kit included MASM 5.1 (a single executable that worked under both MSDOS and OS/2 1.x).
• C 6.0 released in 1989 added support for tiny memory model and better support for the ANSI C89 standard (the documentation explicitly says that it is not 100% compliant but it appears to be close enough for practical purposes). It added the Programmer's Workbench IDE, global flow analysis, a source browser, and a new debugger. To the surprise of many, C++ was not included even though competitors already had offerings.{{cite web | title = Optimizing With Microsoft C 6.0 | date = August 1, 1990 | url = http://www.drdobbs.com/windows/optimizing-with-microsoft-c-60/184408398 | first = Scott Robert | last = Ladd }}
• C/C++ 7.0 was released in 1992. Dropped OS/2 support. Compilation required a 386 processor plus the included DOS extender, 386MAX,{{cite magazine |last=Myers |first=Ben |date=1992-07-01 |title=Microsoft C/C++ |url=https://books.google.com/books?id=X4152M1DLygC&pg=PA387 |magazine=PC Magazine |publisher=Ziff Davis |page=387 |access-date=2023-12-21}} though for users to be able to target DOS extenders in their own programs they write, one of several later-released third-party tools was required.{{cite magazine |author= |title=News/Software Pipeline Announced |url=https://books.google.com/books?id=cTwEAAAAMBAJ&pg=PA17 |magazine=InfoWorld |publisher=InfoWorld Media Group |date=1993-03-15 |access-date=2023-12-21}} Added built-in support for C++ and MFC (Microsoft Foundation Class Library) 1.0.Retrieved from http://support.microsoft.com/kb/196831.
• {{anchor|vc1}}Visual C++ 1.0, which included MFC 2.0, was the first version of "Visual" C++, released in February 1993. It was Cfront 2.1 compliant{{cite news

| title = Visual C++ is a strong development tool

| url = https://books.google.ca/books?id=OjsEAAAAMBAJ&printsec=frontcover&source=gbs_ge_summary_r&cad=0#v=onepage&q=Visual%20C%2B%2B%20is%20a%20strong%20development%20tool&f=false

| newspaper = InfoWorld

| date = 1993-06-21

| page = 94

| access-date = 2025-04-07

}} and available in two editions:

• Standard: replaced QuickC for Windows.
• Professional: replaced C/C++ 7.0. Included the ability to build both DOS and Windows applications, an optimizing compiler, a source profiler, and the Windows 3.1 SDK. The Phar Lap 286 DOS Extender Lite was also included.{{cite news | title = Rival DOS Extenders debut at show | newspaper = InfoWorld | date = March 1, 1993 | page = 18 | url = https://books.google.com/books?id=fzwEAAAAMBAJ }}
• Visual C++ 1.5 was released in December 1993, included MFC 2.5, and added OLE 2.0 and ODBC support to MFC.{{cite news | title = Visual C++ 1.5 integrates OLE, ODBC | newspaper = InfoWorld | date = November 8, 1993 | page = 5 | url = https://books.google.com/books?id=8ToEAAAAMBAJ }} It was the first version of Visual C++ that came only on CD-ROM.
• Visual C++ 1.51 and 1.52 were available as part of a subscription service.
• Visual C++ 1.52b is similar to 1.52, but does not include the Control Development Kit.
• Visual C++ 1.52c was a patched version of 1.5. It is the last, and arguably most popular, development platform for Microsoft Windows 3.x. It is available through Microsoft Developer Network.

• {{anchor|vc1_32}}Visual C++ 1.0 (original name: Visual C++ 32-bit Edition) released in 1993 was the first version for 32-bit development (and requiring 32-bit Windows NT as a host) for the Intel 386 architecture.{{cite news | title = Microsoft set to prerelease 32-bit Visual C++ | newspaper = InfoWorld | date = July 19, 1993 | page = 12 | url = https://books.google.com/books?id=mTsEAAAAMBAJ }} Although released when 16-bit version 1.5 was available, it did not include support for OLE2 and ODBC. It was also available in a bundle called Visual C++ 16/32-bit Suite, which included Visual C++ 1.5.{{cite news | title = C++ IDEs evolve | newspaper = InfoWorld | date = April 4, 1994 | page = 79 | url = https://books.google.com/books?id=FTsEAAAAMBAJ }}
• {{anchor|vc2}}Visual C++ 2.0, which included MFC 3.0, was the first version to be 32-bit only. In many ways, this version was ahead of its time, since Windows 95, then codenamed "Chicago", was not yet released, and Windows NT had only a small market share. Microsoft included and updated Visual C++ 1.5 as part of the 2.x releases up to 2.1, which included Visual C++ 1.52, and both 16-bit and 32-bit version of the Control Development Kit (CDK) were included. Visual C++ 2.x also supported Win32s development. It is available through Microsoft Developer Network. There was a Visual C++ 2.0 RISC Edition for MIPS and Alpha processors, as well as a cross-platform edition for the Macintosh (68000 instruction set).{{cite web|url=http://accu.org/index.php/journals/1771|title=Microsoft Visual C++ Strategy}}
• Microsoft Visual C++ Cross-Development Edition for the Macintosh was an add-on for Visual C++ that introduced the Windows Portability Library, originally known as Windows Library for Macintosh{{rp|pages=17}} or Windows Layer for the Macintosh (WLM),{{ cite web | url=http://www.iowaconsumercase.org/011607/3000/PX03096.pdf | archive-url=https://web.archive.org/web/20070202162055/http://www.iowaconsumercase.org/011607/3000/PX03096.pdf | url-status=dead | archive-date=2007-02-02 | title=Generalized Evangelism Timeline | publisher=Microsoft Corporation| last1=Plamondon | first1=James | date=9 October 1997 | access-date=27 January 2024 }}{{rp | pages=16}} allowing developers to write applications against the Win32 and MFC APIs that could be compiled for 68000 architecture Macintosh computers.{{ cite book | url=https://archive.org/details/crossplatformdev0000cull/page/15/mode/1up | title=Cross-Platform Development Using Visual C++ | publisher=M&T Books | last1=Cullens | first1=Chane | last2=Blackwell | first2=Ken | isbn=1-55851-428-7 | date=1995 | access-date=27 January 2024 }}
• Visual C++ 2.1 and 2.2 were updates for 2.0 available through subscription.
• {{anchor|vc4}}Visual C++ 4.0, released on 1995-12-11,{{cite web|url=http://support.microsoft.com/gp/lifeobsoleteproducts |title=Obsolete Products |url-status=dead |archive-url=https://web.archive.org/web/20050814234847/http://support.microsoft.com/gp/lifeobsoleteproducts |archive-date=2005-08-14 }} introduced the Developer Studio IDE. Its then-novel tiled layout of non-overlapping panels—navigation panel, combination editor/source level debugger panel, and console output panel{{cite book |last=Toth |first=Viktor |title=Visual C++ 4.0 unleashed |url=https://books.google.com/books?id=93o_AQAAIAAJ&q=visual+c%2B%2B+4.0+unleashed |access-date=26 July 2013 |year=1996 |publisher=SAMS Publishing |location=Indianapolis |isbn= 9780672308741 |chapter=1 |chapter-url=http://doc.sumy.ua/prog/unleash4/vcu01fi.htm}}—continues through the Visual Studio product line (as of 2013). Visual C++ 4.0 included MFC 4.0, was designed for Windows 95 and Windows NT. To allow support of legacy (Windows 3.x/DOS) projects, 4.0 came bundled with the Visual C++ 1.52 installation CD. Updates available through subscription included Visual C++ 4.1, which came with the Microsoft Game SDK (later released separately as the DirectX SDK), and Visual C++ 4.2. Version number 3.0 was skipped to achieve version number parity between Visual C++ 4.0 and MFC 4.0.{{cite web|url=http://blogs.msdn.com/ricom/archive/2009/10/07/my-history-of-visual-studio-part-3.aspx|title=History of Visual Studio (Part 3)|date=6 August 2021 }}
• {{anchor|vc42}}Visual C++ 4.2 did not support Windows 3.x (Win32s) development.{{cite web|url=http://msdn.microsoft.com/en-us/library/aa697418(VS.71).aspx|title=Major Changes from Visual C++ 4.0 to 4.2 |access-date=2018-04-18 |archive-url=https://web.archive.org/web/20100228175137/http://msdn.microsoft.com/en-us/library/aa697418(VS.71).aspx |archive-date=2010-02-28}} This was the final version with a cross-platform edition for the Mac available and it differed from the 2.x version in that it also allowed compilation for the PowerPC instruction set.
• {{anchor|vc5}}Visual C++ 5.0 (bundled with Visual Studio 97) which included MFC 4.21 and was released 1997-04-28, was a major upgrade from 4.2.{{cite web|url=http://msdn.microsoft.com/en-us/library/aa697419(VS.71).aspx|title=Major Changes from Visual C++ 4.2 to 5.0}} Available in four editions: Learning,{{cite web|url=http://www.microsoft.com/products/prodref/199_ov.htm|title=Microsoft Visual C++ 5.0 Learning Edition|website=Microsoft |archive-url=https://web.archive.org/web/19990427114135/http://www.microsoft.com/products/prodref/199_ov.htm|archive-date=April 27, 1999}} Professional,{{cite web|url=http://www.microsoft.com/products/prodref/197_ov.htm|title=Microsoft Visual C++ 5.0 Professional Edition|website=Microsoft |archive-url=https://web.archive.org/web/19990427101205/http://www.microsoft.com/products/prodref/197_ov.htm|archive-date=April 27, 1999}} Enterprise,{{cite web|url=http://www.microsoft.com/products/prodref/198_ov.htm|title=Microsoft Visual C++ 5.0 Enterprise Edition|website=Microsoft |archive-url=https://web.archive.org/web/19990417134138/http://www.microsoft.com/products/prodref/198_ov.htm|archive-date=April 17, 1999}} and RISC.{{cite web|url=http://www.microsoft.com/products/prodref/501_ov.htm|title=Microsoft Visual C++ 5.0 RISC Edition|website=Microsoft |archive-url=https://web.archive.org/web/19990429121236/http://www.microsoft.com/products/prodref/501_ov.htm|archive-date=April 29, 1999}}
• {{anchor|vc6}}Visual C++ 6.0 (commonly known as VC6, and available standalone in Standard, Professional and Enterprise editions, as well as bundled with Visual Studio 6.0), which included MFC 6.0, was released in 1998.{{cite news |url=https://www.justice.gov/opa/press-release/file/1092091/download |title=Criminal Complaint |date=June 8, 2018 |first=Nathan P. |last=Shields |publisher=United States Department of Justice |page=128 |quote=This alone is not a dispositive link, as Visual C++ 6.0, released in 1998, still has proponents mostly because it does not require the installation of Microsoft’s .NET framework in order to run, as later versions of Visual C++ do.}}{{cite web|url=http://msdn.microsoft.com/en-us/library/aa729389(VS.71).aspx|title=Major Changes from Visual C++ 5.0 to 6.0|archive-url=https://web.archive.org/web/20080914202003/http://msdn.microsoft.com/en-us/library/aa729389(VS.71).aspx|archive-date=September 14, 2008}} The release was somewhat controversial since it did not include an expected update to MFC. Visual C++ 6.0 is still quite popular and often used to maintain legacy projects. There are, however, issues with this version under Windows XP, especially under the debugging mode (for example, the values of static variables do not display). The debugging issues can be solved with a patch called the "Visual C++ 6.0 Processor Pack".This page stresses that Users must also be running Windows 98, Windows NT 4.0, or Windows 2000. Retrieved from http://msdn2.microsoft.com/en-us/vstudio/aa718349.aspx. Version number: 12.00.8804
• {{anchor|vc7}}Visual C++ .NET 2002 (also known as Visual C++ 7.0), which included MFC 7.0, was released in 2002 with support for link time code generation and debugging runtime checks, .NET 1.0, and Visual C# and Managed C++. The new user interface used many of the hot keys and conventions of Visual Basic, which accounted for some of its unpopularity among C++ developers.{{Citation needed|date=May 2010}} Version number: 13.00.9466
• {{anchor|vc71}}Visual C++ .NET 2003 (also known as Visual C++ 7.1), which included MFC 7.1, was released in 2003 along with .NET 1.1 and was a major upgrade to Visual C++ .NET 2002, and was the first version to support the C99 "long long" construct. It was considered a patch to Visual C++ .NET 2002. Accordingly, the English language upgrade version of Visual Studio .NET 2003 shipped for minimal cost to owners of the English-language version of Visual Studio .NET 2002. Windows 98 is the lowest officially supported version. Although simple programs will work on Windows 95 and NT 4.0, more complex programs may cause things like ws2_32.dll to be referenced, or functions missing in kernel32.dll. In later versions (Visual C++ 2005) of the compiler even simple programs won't work (unless you replace the C library) because they have a reference to function IsDebuggerPresent in kernel32.dll which only exists in Windows 98 and later.{{Citation needed|date=May 2010}} Version number: 13.10.3077
• eMbedded Visual C++Douglas Boling :Programming Microsoft Windows CE .NET, Third Edition Microsoft Press; 3rd edition (June 25, 2003) Paperback: 1264 pages {{ISBN|978-0735618848}} - [http://examples.oreilly.de/english_examples/9780735618848/cd_contents/Readme.txt Companion CD with Microsoft eMbedded Visual C++ 4.0 Service Pack 2] {{webarchive|url=https://archive.today/20130211131045/http://examples.oreilly.de/english_examples/9780735618848/cd_contents/Readme.txt |date=2013-02-11 }} in various versions was used to develop for some versions of the Windows CE operating system. Initially it replaced a development environment consisting of tools added onto Visual C++ 6.0. eMbedded Visual C++ was replaced as a separate development environment by Microsoft Visual Studio 2005.

• {{anchor|vc8}}Visual C++ 2005 (also known as Visual C++ 8.0), which included MFC 8.0, was released in November 2005. This version supports .NET 2.0 and includes a new version of C++ targeted to the .NET framework (C++/CLI) with the purpose of replacing the previous version (Managed C++). Managed C++ for CLI is still available via compiler options, though. It also introduced OpenMP. With Visual C++ 2005, Microsoft also introduced Team Foundation Server. Visual C++ 8.0 has problems compiling MFC AppWizard projects that were created using Visual Studio 6.0, so maintenance of legacy projects can be continued with the original IDE if rewriting is not feasible. Visual C++ 2005 is the last version able to target Windows 98 and Windows Me.[http://msdn.microsoft.com/en-us/library/6sehtctf(v=VS.90).aspx How to: Modify WINVER and _WIN32_WINNT][http://msdn.microsoft.com/en-us/library/bb531344(v=VS.90).aspx Breaking Changes] SP1 version (14.00.50727.762) is also available in Microsoft Windows SDK Update for Windows Vista.
• {{anchor|vc9}}Visual C++ 2008 (also known as Visual C++ 9.0) was released in November 2007. This version supports .NET 3.5. Managed C++ for CLI is still available via compiler options. By default, all applications compiled against the Visual C++ 2008 Runtimes (static and dynamic linking) will only work on Windows 2000, Windows XP SP2 and later.[http://msdn.microsoft.com/en-us/library/ws0swas0(VS.100).aspx Windows Platforms (CRT)]{{cite web|url=http://msdn.microsoft.com/en-us/library/bb531344.aspx?ppud=4|title=Visual C++ 2008 Breaking Changes|date=25 May 2023 }} A feature pack released for VC9, later included in SP1, added support for C++ TR1 library extensions. SP1 version (15.00.30729.01) is also available in Microsoft Windows SDK for Windows 7.
• Some versions of Visual C++ supported Itanium 2.
• {{anchor|vc10}}Visual C++ 2010 (also known as Visual C++ 10.0) was released on April 12, 2010. It uses a SQL Server Compact database to store information about the source code, including IntelliSense information, for better IntelliSense and code-completion support.{{cite web | title = IntelliSense, part 2: The Future | url = http://blogs.msdn.com/vcblog/archive/2008/02/29/intellisense-part-2-the-future.aspx | author = Visual C++ Team Blog | access-date =March 12, 2008}} However, Visual C++ 2010 does not support Intellisense for C++/CLI.{{cite web | url = http://blogs.msdn.com/b/vcblog/archive/2011/03/03/10136696.aspx | title = Why IntelliSense is not supported for C++/CLI in Visual Studio 2010 | access-date =March 13, 2011}} This version adds a C++ parallel computing library called the Parallel Patterns Library, partial support for C++11, significantly improved IntelliSense based on the Edison Design Group front end,{{cite web | title = Rebuilding Intellisense | url = http://blogs.msdn.com/b/vcblog/archive/2009/05/27/rebuilding-intellisense.aspx | author = Visual C++ Team Blog | date = 27 May 2009 }} and performance improvements to both the compiler and generated code.{{cite web | title = Visual C++ Code Generation in Visual Studio 2010 | url = http://blogs.msdn.com/vcblog/archive/2009/11/02/visual-c-code-generation-in-visual-studio-2010.aspx | author = Visual C++ Team Blog}} This version is built on .NET 4.0, but supports compiling to machine code. The partial C++11 support mainly consists of six compiler features:{{cite web | url = http://blogs.msdn.com/vcblog/archive/2010/04/06/c-0x-core-language-features-in-vc10-the-table.aspx | title = C++0x Core Language Features In VC10: The Table}} lambdas, rvalue references, auto, decltype, static_assert, and nullptr. C++11 also supports library features (e.g., moving the TR1 components from std::tr1 namespace directly to std namespace). Variadic templates were also considered, but delayed until some future version due to having a lower priority, which stemmed from the fact that, unlike other costly-to-implement features (lambda, rvalue references), variadic templates would benefit only a minority of library writers rather than the majority of compiler end users.{{cite web | title = Stephan T. Lavavej: Everything you ever wanted to know about nullptr | url = http://channel9.msdn.com/shows/Going+Deep/Stephan-T-Lavavej-Everything-you-ever-wanted-to-know-about-nullptr/}} By default, all applications compiled against Visual C++ 2010 Runtimes only work on Windows XP SP2 and later. The RTM version (16.00.30319) is also available in Windows SDK for Windows 7 and .NET Framework 4 (WinSDK v7.1).{{cite web | title = Released: Windows SDK for Windows 7 and .NET Framework 4 | url = http://blogs.msdn.com/b/windowssdk/archive/2010/05/25/released-windows-sdk-for-windows-7-and-net-framework-4.aspx | author = Microsoft Windows SDK Blog}} SP1 version (16.00.40219) is available as part of Visual Studio 2010 Service Pack 1 or through the Microsoft Visual C++ 2010 Service Pack 1 Compiler Update for the Windows SDK 7.1.[http://support.microsoft.com/kb/2519277/en-us FIX: Visual C++ compilers are removed when you upgrade Visual Studio 2010 Professional or Visual Studio 2010 Express to Visual Studio 2010 SP1 if Windows SDK v7.1 is installed]
• {{anchor|vc11}}Visual C++ 2012 (also known as Visual C++ 11.0) was released on August 15, 2012. It features improved C++11 support, and support for Windows Runtime development.{{cite web |url=https://msdn.microsoft.com/en-us/library/vstudio/hh409293(v=vs.110).aspx |title=What's New for Visual C++ in Visual Studio 2012 |author= |publisher=Microsoft |work=Microsoft Developer Network |date=29 November 2012 |access-date=September 20, 2015}}
• {{anchor|vc12}}Visual C++ 2013 (also known as Visual C++ 12.0) was released on October 17, 2013. It features further C++11 and C99 support, and introduces a REST SDK.{{cite web |url=https://msdn.microsoft.com/en-us/library/vstudio/hh409293(v=vs.120).aspx |title=What's New for Visual C++ in Visual Studio 2013 |author= |publisher=Microsoft |work=Microsoft Developer Network |date=28 April 2015 |access-date=September 20, 2015}}
• {{anchor|vc14}}Visual C++ 2015 (also known as Visual C++ 14.0) was released on July 20, 2015.{{cite web|url=http://blogs.msdn.com/b/vcblog/archive/2015/07/20/visual-studio-2015-rtm-now-available.aspx|title=Visual Studio 2015 RTM Now Available|author=Eric Battalio|date=July 20, 2015|publisher=Microsoft|work=Visual C++ Team Blog}} It features improved C++11/14/17 support.{{cite web|url=http://blogs.msdn.com/b/vcblog/archive/2015/06/19/c-11-14-17-features-in-vs-2015-rtm.aspx|title=C++11/14/17 Features In VS 2015 RTM|author=Stephan T. Lavavej|date=June 19, 2015|publisher=Microsoft|work=Visual C++ Team Blog}} Without any announcement from Microsoft, Visual Studio 2015 Update 2 started generating telemetry calls in compiled binaries. After some users contacted Microsoft about this problem, Microsoft said they would remove these telemetry calls when compiling with the future Visual Studio 2015 Update 3.[https://www.infoq.com/news/2016/06/visual-cpp-telemetry Reviewing Microsoft's Automatic Insertion of Telemetry into C++ Binaries]{{Cite web|url=https://www.reddit.com/r/cpp/comments/4ibauu/visual_studio_adding_telemetry_function_calls_to/d30dmvu|title=Visual Studio adding telemetry function calls to binary? • /r/cpp|website=reddit|date=7 May 2016|access-date=2016-08-17}} The function in question was removed from the Visual C++ CRT static libraries in Visual Studio 2015 Update 3.{{Citation needed|date=August 2016}}
• {{anchor|vc14}}Visual C++ 2017 (also known as Visual C++ 14.1) was released on March 7, 2017.{{cite web|url=https://devblogs.microsoft.com/visualstudio/announcing-visual-studio-2017-general-availability-and-more/|title=Announcing Visual Studio 2017 General Availability… and more|author=Julia Liuson|date=March 7, 2017|publisher=Microsoft|work=Visual Studio Team Blog}}
• {{anchor|vc16}}Visual C++ 2019 (also known as Visual C++ 14.20) was released on April 2, 2019.{{cite web|url=https://devblogs.microsoft.com/visualstudio/join-us-april-2nd-for-the-launch-of-visual-studio-2019/|title=Join us April 2nd for the Launch of Visual Studio 2019!|author=Amanda Silver|date=February 14, 2019|publisher=Microsoft|work=Visual Studio Team Blog}}
• {{anchor|vc17}}Visual C++ 2022 (also known as Visual C++ 14.30) was released on November 8, 2021.{{cite web|url=https://devblogs.microsoft.com/visualstudio/visual-studio-2022-now-available/|title=Visual Studio 2022 now available|author=Amanda Silver|date=November 8, 2021|publisher=Microsoft|work=Visual Studio Team Blog}}

There are several different version numbers to consider when working with Visual C or C++. The oldest and most original of these is the compiler version number, which has been monotonically increased since the early Microsoft C compiler days. This is the version returned by running the command cl.exe on its own without any options. By taking two digits after the decimal and dropping the decimal point, this also becomes the value of the C pre-processor macro: _MSC_VER, and the CMake variable: MSVC_VERSION. A longer version of the C macro is _MSC_FULL_VER to make more finely-grained distinctions between builds of the compiler. An example of _MSC_VER is 1933 to represent version 19.33 of the Microsoft C/C++ compiler, and of _MSC_FULL_VER is 193331630.

The Visual product version, such as "17.3.4", designates the version of Visual Studio with which version 19.33 of the compiler was packaged. Then there is the Microsoft Visual C/C++ Runtime Library version, e.g. "14.3". From this, one can also deduce the toolset version, which can be obtained by taking the first three digits of the runtime library version and dropping the decimal, e.g. "143". It includes the Visual C/C++ runtime library, as well as compilers, linkers, assemblers, other build tools, and matching libraries and header files. The following is a (scrapeable) table of the known correlated version numbers.

The Visual C++ compiler ABI has historically changed between major compiler releases.Microsoft MSDN: [http://msdn.microsoft.com/en-us/library/bb531344.aspx Breaking Changes in Visual C++] This is especially the case for STL containers, where container sizes have varied a lot between compiler releases.Microsoft MSDN: [http://msdn.microsoft.com/en-us/library/vstudio/hh438470.aspx Containers (Modern C++)] Microsoft therefore recommends against using C++ interfaces at module boundaries when one wants to enable client code compiled using a different compiler version. Instead of C++, Microsoft recommends using CMicrosoft MSDN: [http://msdn.microsoft.com/en-us/library/vstudio/hh438475.aspx Portability At ABI Boundaries (Modern C++)] or COMMicrosoft forum: [http://social.msdn.microsoft.com/Forums/en/vcgeneral/thread/86eda6a7-4d90-4e19-a9d4-6cbe22b661f4 Binary compatibility across Visual C++ versions] {{Webarchive|url=https://archive.today/20130216110824/http://social.msdn.microsoft.com/Forums/en/vcgeneral/thread/86eda6a7-4d90-4e19-a9d4-6cbe22b661f4 |date=2013-02-16 }} interfaces, which are designed to have a stable ABI between compiler releases.

All 14.x MSVC releases have a stable ABI,docs.microsoft.com: [https://docs.microsoft.com/en-us/cpp/porting/binary-compat-2015-2017? C++ binary compatibility between Visual Studio 2015, 2017, and 2019] and binaries built with these versions can be mixed in a forwards-compatible manner, noting the following restrictions:

• The toolset version used must be equal to or higher than the highest toolset version used to build any linked binaries.
• The MSVC Redistributable version must be equal to or higher than the toolset version used by any application component.
• Static libraries or object files compiled with /GL (Whole program optimisation) are not binary compatible between versions and must use the exact same toolset.

Visual C++ ships with different versions of C runtime libraries.[http://msdn.microsoft.com/en-us/library/abx4dbyh.aspx C Run-Time Libraries] This means users can compile their code with any of the available libraries. However, this can cause some problems when using different components (DLLs, EXEs) in the same program. A typical example is a program using different libraries. The user should use the same C Run-Time for all the program's components unless the implications are understood. Microsoft recommends using the multithreaded, dynamic link library (/MD or /MDd compiler option) to avoid possible problems.

Although Microsoft's CRT implements a large subset of POSIX interfaces, the Visual C++ compiler will emit a warning on every use of such functions by default. The rationale is that C and C++ standards require an underscore prefix before implementation-defined interfaces, so the use of these functions are non-standard.{{cite web |title=Compatibility |url=https://docs.microsoft.com/en-us/cpp/c-runtime-library/compatibility |website=Microsoft: CRT library features |date=26 October 2022 |language=en-us}} However, systems that are actually POSIX-compliant would not accept these underscored names, and it is more portable to just turn off the warning instead.

Although the product originated as an IDE for the C programming language, for many years the compiler's support for that language conformed only to the original edition of the C standard, dating from 1989, but not the C99 revision of the standard. There had been no plans to support C99 even in 2011, more than a decade after its publication.{{cite web|url=https://connect.microsoft.com/VisualStudio/feedback/details/653336/c99-support|title=C99 support|work=Microsoft Connect|archive-url=https://web.archive.org/web/20160304185822/http://connect.microsoft.com/VisualStudio/feedback/details/653336/c99-support|archive-date=2016-03-04|url-status=dead|access-date=2015-09-21}}

Visual C++ 2013 finally added support for various C99 features in its C mode (including designated initializers, compound literals, and the _Bool type),{{cite web|title=What's New for Visual C++ in Visual Studio 2013|url=https://msdn.microsoft.com/en-us/library/hh409293(v=vs.120).aspx|work=Microsoft Developer Network| date=28 April 2015 |publisher=Microsoft}} though it was still not complete.{{cite web|url=http://blogs.msdn.com/b/vcblog/archive/2013/07/19/c99-library-support-in-visual-studio-2013.aspx|title=C99 library support in Visual Studio 2013|author=Pat Brenner|date=July 19, 2013|publisher=Microsoft|work=Visual C++ Team Blog}} Visual C++ 2015 further improved the C99 support, with full support of the C99 Standard Library, except for features that require C99 language features not yet supported by the compiler.{{cite web|url=https://msdn.microsoft.com/en-us/library/hh409293(v=vs.140).aspx|title=What's New for Visual C++ in Visual Studio 2015|work=Microsoft Developer Network|date=3 January 2018 |publisher=Microsoft}}

Most of the changes from the C11 revision of the standard were still not supported by Visual C++ 2017.{{cite web|url=https://docs.microsoft.com/en-us/cpp/build/walkthrough-compile-a-c-program-on-the-command-line|title=Walkthrough: Compile a C program on the command line|work=Visual C++ Documentation|date=10 May 2022 |publisher=Microsoft}} For example, generic selections via the _Generic keyword are not supported by the compiler and result in a syntax error.{{cite web|url=https://developercommunity.visualstudio.com/content/problem/250665/msvc-2017-does-not-support-generic-type-generic-ma.html|title=MSVC 2017 does not support _Generic (type generic macros) in C}}

The preprocessor was overhauled in 2018, with C11 in sight:{{cite web |last=Luvsanbat |first=Bat-Ulzii |date=July 6, 2018 |title=MSVC Preprocessor Progress towards Conformance |url=https://devblogs.microsoft.com/cppblog/msvc-preprocessor-progress-towards-conformance/ |publisher=Microsoft |work=Visual Studio Team Blog |url-status=live |archive-url=https://web.archive.org/web/20240303170213/https://devblogs.microsoft.com/cppblog/msvc-preprocessor-progress-towards-conformance/ |archive-date=3 Mar 2024}}

{{blockquote|Full C11 conformance is on our roadmap, and updating the preprocessor is just the first step in that process. The C11 _Generic feature is not actually part of the preprocessor, so it has not yet been implemented. When implemented I expect the feature to work independently of if the traditional or updated preprocessor logic is used.}}

_Generic support has been committed to MSVC as of February 2020.{{cite web|url=https://www.reddit.com/r/cpp/comments/hjn4uv/c20_features_and_fixes_in_vs_2019_161_through_166/fwsil0q/?context=3 |title=C++20 Features and Fixes |date=July 3, 2020 |website=reddit}}

In September 2020, Microsoft announced C11 and C17 standards support in MSVC would arrive in version 16.8.{{cite web|url=https://devblogs.microsoft.com/cppblog/c11-and-c17-standard-support-arriving-in-msvc/|title=C11 and C17 Standard Support Arriving in MSVC|date=September 14, 2020}} This did not include optional features but Microsoft indicated that they were planning to add support for atomics and threads at a later date. In version 17.5, partial (since atomic locks are missing) and experimental (meaning hidden behind the compiler flag /experimental:c11atomics) support for atomics was added{{cite web|url=https://devblogs.microsoft.com/cppblog/c11-atomics-in-visual-studio-2022-version-17-5-preview-2/|title=C11 Atomics in Visual Studio 2022 version 17.5 Preview 2|date=2022-12-13}} and in version 17.8, support for threads was added, this time not behind a compiler flag.{{cite web|url=https://devblogs.microsoft.com/cppblog/c11-threads-in-visual-studio-2022-version-17-8-preview-2/|title=C11 Threads in Visual Studio 2022 version 17.8 Preview 2|date=2023-09-26}}{{Cite web |last=Murphy |first=Adrian |date=2023-11-14 |title=Visual Studio 17.8 now available! |url=https://devblogs.microsoft.com/visualstudio/visual-studio-17-8-now-available/ |access-date=2024-01-12 |website=Visual Studio Blog |language=en-US}}

With default settings MSVC does not do two-phase name lookup which prevents it from flagging a wide range of invalid code. Most checks are deferred to template instantiation. More recent versions remedy this behavior, but it needs to be enabled by the command-line option /permissive-.{{cite web|url=https://devblogs.microsoft.com/cppblog/two-phase-name-lookup-support-comes-to-msvc/|title=Two-phase name lookup support comes to MSVC|date=2017-09-11}}

Describing it as "excellent", BYTE in February 1989 approved of Microsoft C 5.1's OS/2 support, QuickC for interactive development, and CodeView debugger. Although Watcom C produced slightly faster code, the magazine said that developers "might still prefer Microsoft's friendlier and more powerful tools".{{Cite magazine |last1=Apiki |first1=Steven |last2=Udell |first2=Jon |date=February 1989 |title=Smoothing Out C |url=https://archive.org/details/eu_BYTE-1989-02_OCR/page/n225/mode/1up?view=theater |access-date=2024-10-08 |magazine=BYTE |pages=170–186}}

{{Reflist|30em}}

{{Refbegin}}

• {{Cite web |url=https://docs.microsoft.com/en-us/archive/blogs/brianjo/building-win32-applications-using-visual-c-2005-express |title=Building Win32 Applications Using Visual C++ 2005 Express |date=8 August 2004 |first=Brian |last=Johnson |work=Brian Johnson's Startup Developer Blog |via=Microsoft Docs Archive |publisher=Microsoft}}
• {{Cite web |url=https://devblogs.microsoft.com/cppblog/rejuvenating-the-microsoft-cc-compiler/ |title=Rejuvenating the Microsoft C/C++ Compiler |first=Jim |last=Springfield |work=C++ Team Blog |publisher=Microsoft |date=25 September 2015}}

{{Refend}}

• {{Official website|https://docs.microsoft.com/en-us/cpp/}}
• [https://docs.microsoft.com/en-us/cpp/overview/visual-cpp-tools-and-features-in-visual-studio-editions?redirectedfrom=MSDN&view=vs-2019 C++ Tools and Features in Visual Studio Editions]
• [https://visualstudio.microsoft.com/visual-cpp-build-tools/ Microsoft C++ Build Tools]
• [http://channel9.msdn.com/Shows/C9-GoingNative C9::GoingNative] on Microsoft Channel 9

{{MS DevTools}}

{{C programming language}}

{{C++ programming language}}

{{Authority control}}

Category:1993 software

Category:C (programming language) compilers

Category:C++ compilers

Category:Integrated development environments

Visual C++

C++