Microsoft Visual C++

Visual C++

Developer(s)	Microsoft
Initial release	February 1993;31 years ago (1993-02) [1]
Stable release	14.40.33617
Written in	C++ [2]
Operating system	Windows
Platform	IA-32, x86-64 and ARM
Available in	English, Chinese (Simplified & Traditional), Czech, French, German, Italian, Japanese, Korean, Polish, Portuguese (Brazilian), Russian, Spanish, Turkish
Type	Compiler
License	Trialware and freeware
Website	docs.microsoft.com/en-us/cpp/

Microsoft Visual C++ (MSVC) is a compiler for the C, C++, C++/CLI and C++/CX programming languages by Microsoft. MSVC is proprietary software; it was originally a standalone product but later became a part of Visual Studio and made available in both trialware and freeware forms. It features tools for developing and debugging C++ code, especially code written for the Windows API, DirectX and .NET.

Many applications require redistributable Visual C++ runtime library packages to function correctly. These packages are frequently installed separately from the applications they support, enabling multiple applications to use the package with only a single installation. These Visual C++ redistributable and runtime packages are mostly installed for standard libraries that many applications use. ^[3]

History

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 ]}

16-bit versions

• 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. ^[4]
• C 3.0 was the first version developed inside Microsoft. ^[5] 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. ^[6]
• C/C++ 7.0 was released in 1992. Dropped OS/2 support. Compilation required a 386 processor plus the included DOS extender, 386MAX, ^[7] 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. ^[8] Added built-in support for C++ and MFC (Microsoft Foundation Class Library) 1.0. ^[9]
• 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 ^[10] and available in two editions: ^[1]
  • 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. ^[10] The Phar Lap 286 DOS Extender Lite was also included. ^[11]
• Visual C++ 1.5 was released in December 1993, included MFC 2.5, and added OLE 2.0 and ODBC support to MFC. ^[12] 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.

Strictly 32-bit versions

• Visual C++ 1.0 (original name: Visual C++ 32-bit Edition) released in 1993 was the first version for 32-bit development for the Intel 386 architecture. ^[13] 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. ^[14]
• 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). ^[15]
  • 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 ^{[16] : 17} or Windows Layer for the Macintosh (WLM), ^{[17] : 16} allowing developers to write applications against the Win32 and MFC APIs that could be compiled for 68000 architecture Macintosh computers. ^[16]
  • Visual C++ 2.1 and 2.2 were updates for 2.0 available through subscription.
• Visual C++ 4.0, released on 1995-12-11, ^[18] 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 ^[19] —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. ^[20]
• Visual C++ 4.2 did not support Windows 3.x (Win32s) development. ^[21] 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.
• Visual C++ 5.0 (bundled with Visual Studio 97) which included MFC 4.21 and was released 1997-04-28, ^[18] was a major upgrade from 4.2. ^[22] Available in four editions: Learning, ^[23] Professional, ^[24] Enterprise, ^[25] and RISC. ^[26]
• 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. ^{[27] [28]} 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". ^[29] Version number: 12.00.8804
• 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 ]} Version number: 13.00.9466
• 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 ]} Version number: 13.10.3077
• eMbedded Visual C++ ^[30] 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.

32-bit and 64-bit versions

• 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. ^{[31] [32]} SP1 version (14.00.50727.762) is also available in Microsoft Windows SDK Update for Windows Vista.
• 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. ^{[33] [34]} 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.
• 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. ^[35] However, Visual C++ 2010 does not support Intellisense for C++/CLI. ^[36] 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, ^[37] and performance improvements to both the compiler and generated code. ^[38] 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: ^[39] 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. ^[40] 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). ^[41] 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. ^[42]
• 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. ^[43]
• 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. ^[44]
• Visual C++ 2015 (also known as Visual C++ 14.0) was released on July 20, 2015. ^[45] It features improved C++11/14/17 support. ^[46] 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. ^{[47] [48]} The function in question was removed from the Visual C++ CRT static libraries in Visual Studio 2015 Update 3.^{[ citation needed ]}
• Visual C++ 2017 (also known as Visual C++ 14.1) was released on March 7, 2017. ^[49]
• Visual C++ 2019 (also known as Visual C++ 14.20) was released on April 2, 2019. ^[50]
• Visual C++ 2022 (also known as Visual C++ 14.30) was released on November 8, 2021. ^[51]

Internal version numbering

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". You should use the >= operator to test the value of _MSC_VER or _MSC_FULL_VER instead of equality.

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 deduce also 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.

Visual Studio Versions ^{[52] [53]}

product name	VC ( Version Code )	marketing year	_MSC_VER	_MSC_FULL_VER	runtime library version
Microsoft C 6.0			600
Microsoft C/C++ 7.0			700
Visual C++ 1.0	1.0		800		1
Visual C++ 2.0	2.0		900		2
Visual C++ 4.0	4.0		1000		4
Visual C++ 4.1	4.1		1010		4.1
Visual C++ 4.2	4.2		1020		4.2
Visual Studio 97 [5.0]	5.0	97	1100		5
Visual Studio 6.0 SP5	6.0		1200	12008804	6
Visual Studio 6.0 SP6	6.0		1200	12008804	6
Visual Studio .NET 2002 [7.0]	7.0	2002	1300	13009466	7
Visual Studio .NET 2003 Beta [7.1]	7.1	2003	1310	13102292	7.1
Visual Studio Toolkit 2003 [7.1]	7.1	2003	1310	13103052	7.1
Visual Studio .NET 2003 [7.1]	7.1	2003	1310	13103077	7.1
Visual Studio .NET 2003 SP1 [7.1]	7.1	2003	1310	13106030	7.1
Visual Studio 2005 Beta 1 [8.0]	8.0	2005	1400	140040607	8
Visual Studio 2005 Beta 2 [8.0]	8.0	2005	1400	140050215	8
Visual Studio 2005 [8.0]	8.0	2005	1400	140050320	8
Visual Studio 2005 SP1 [8.0]	8.0	2005	1400	140050727	8
Visual Studio 2008 Beta 2 [9.0]	8.0	2008	1500	150020706	9
Visual Studio 2008 [9.0]	9.0	2010	1500	150021022	9
Visual Studio 2008 SP1 [9.0]	9.0	2010	1500	150030729	9
Visual Studio 2010 Beta 1 [10.0]	10.0	2010	1600	160020506	10
Visual Studio 2010 Beta 2 [10.0]	10.0	2010	1600	160021003	10
Visual Studio 2010 [10.0]	10.0	2010	1600	160030319	10
Visual Studio 2010 SP1 [10.0]	10.0	2010	1600	160040219	10
Visual Studio 2012 [11.0]	11.0	2012	1700	170050727	11
Visual Studio 2012 Update 1 [11.0]	11.0	2012	1700	170051106	11
Visual Studio 2012 Update 2 [11.0]	11.0	2012	1700	170060315	11
Visual Studio 2012 Update 3 [11.0]	11.0	2012	1700	170060610	11
Visual Studio 2012 Update 4 [11.0]	11.0	2012	1700	170061030	11
Visual Studio 2012 November CTP [11.0]	11.0	2012	1700	170051025	11
Visual Studio 2013 Preview [12.0]	12.0	2013	1800	180020617	12
Visual Studio 2013 RC [12.0]	12.0	2013	1800	180020827	12
Visual Studio 2013 [12.0]	12.0	2013	1800	180021005	12
Visual Studio 2013 Update 1 [12.0]	12.0	2013	1800	180021005	12
Visual Studio 2013 Update2 RC [12.0]	12.0	2013	1800	180030324	12
Visual Studio 2013 Update 2 [12.0]	12.0	2013	1800	180030501	12
Visual Studio 2013 Update 3 [12.0]	12.0	2013	1800	180030723	12
Visual Studio 2013 Update 4 [12.0]	12.0	2013	1800	180031101	12
Visual Studio 2013 Update 5 [12.0]	12.0	2013	1800	180040629	12
Visual Studio 2013 November CTP [12.0]	12.0	2013	1800	180021114	12
Visual Studio 2015 [14.0]	14.0	2015	1900	190023026	14
Visual Studio 2015 Update 1 [14.0]	14.0	2015	1900	190023506	14
Visual Studio 2015 Update 2 [14.0]	14.0	2015	1900	190023918	14
Visual Studio 2015 Update 3 [14.0]	14.0	2015	1900	190024210	14
Visual Studio 2017 version 15.0	15.0	2017	1910	191025017	14.1
Visual Studio 2017 version 15.1	15.1	2017	1910	191025017	14.1
Visual Studio 2017 version 15.2	15.2	2017	1910	191025017	14.1
Visual Studio 2017 version 15.3.3	15.3.3	2017	1911	191125507	14.11
Visual Studio 2017 version 15.4.4	15.4.4	2017	1911	191125542	14.11
Visual Studio 2017 version 15.4.5	15.4.5	2017	1911	191125547	14.11
Visual Studio 2017 version 15.5.2	15.5.2	2017	1912	191225831	14.12
Visual Studio 2017 version 15.5.3	15.5.3	2017	1912	191225834	14.12
Visual Studio 2017 version 15.5.4	15.5.4	2017	1912	191225834	14.12
Visual Studio 2017 version 15.5.6	15.5.6	2017	1912	191225835	14.12
Visual Studio 2017 version 15.5.7	15.5.7	2017	1912	191225835	14.12
Visual Studio 2017 version 15.6.0	15.6.0	2017	1913	191326128	14.13
Visual Studio 2017 version 15.6.1	15.6.1	2017	1913	191326128	14.13
Visual Studio 2017 version 15.6.2	15.6.2	2017	1913	191326128	14.13
Visual Studio 2017 version 15.6.3	15.6.3	2017	1913	191326129	14.13
Visual Studio 2017 version 15.6.4	15.6.4	2017	1913	191326129	14.13
Visual Studio 2017 version 15.6.6	15.6.6	2017	1913	191326131	14.13
Visual Studio 2017 version 15.6.7	15.6.7	2017	1913	191326132	14.13
Visual Studio 2017 version 15.7.1	15.7.1	2017	1914	191426428	14.14
Visual Studio 2017 version 15.7.2	15.7.2	2017	1914	191426429	14.14
Visual Studio 2017 version 15.7.3	15.7.3	2017	1914	191426430	14.14
Visual Studio 2017 version 15.7.5	15.7.5	2017	1914	191426433	14.14
Visual Studio 2017 version 15.9.1	15.9.1	2017	1916	191627023	14.16
Visual Studio 2017 version 15.9.4	15.9.4	2017	1916	191627025	14.16
Visual Studio 2017 version 15.9.5	15.9.5	2017	1916	191627026	14.16
Visual Studio 2017 version 15.9.7	15.9.7	2017	1916	191627027	14.16
Visual Studio 2017 version 15.9.11	15.9.11	2017	1916	191627030	14.16
Visual Studio 2019 version 16.0.0	16.0.0	2019	1920	192027508	14.20
Visual Studio 2019 version 16.1.2	16.1.2	2019	1921	192127702	14.21
Visual Studio 2019 version 16.2.3	16.2.3	2019	1922	192227905	14.21
Visual Studio 2019 version 16.3.2	16.3.2	2019	1923	192328105	14.21
Visual Studio 2019 version 16.4.0	16.4.0	2019	1924	192428314	14.24
Visual Studio 2019 version 16.5.1	16.5.1	2019	1925	192528611	14.25
Visual Studio 2019 version 16.6.2	16.6.2	2019	1926	192628806	14.26
Visual Studio 2019 version 16.7	16.7	2019	1927	192729112	14.27
Visual Studio 2019 version 16.8.1	16.8.1	2019	1928	192829333	14.28
Visual Studio 2019 version 16.8.2	16.8.2	2019	1928	192829334	14.28
Visual Studio 2019 version 16.9.0	16.9.0	2019	1928	192829910	14.28
Visual Studio 2019 version 16.9.2	16.9.2	2019	1928	192829913	14.28
Visual Studio 2019 version 16.9.17	16.9.17	2019	1928	192829921	14.28
Visual Studio 2019 version 16.9.18	16.9.18	2019	1928	192829921	14.28
Visual Studio 2019 version 16.9.19	16.9.19	2019	1928	192829923	14.28
Visual Studio 2019 version 16.11.2	16.11.2	2019	1929	192930133	14.29
Visual Studio 2019 version 16.11.8	16.11.8	2019	1929	192930138	14.29
Visual Studio 2019 version 16.11.9	16.11.9	2019	1929	192930139	14.29
Visual Studio 2019 version 16.11.10	16.11.10	2019	1929	192930140	14.29
Visual Studio 2019 version 16.11.11	16.11.11	2019	1929	192930141	14.29
Visual Studio 2019 version 16.11.12	16.11.12	2019	1929	192930142	14.29
Visual Studio 2019 version 16.11.16	16.11.16	2019	1929	192930145	14.29
Visual Studio 2019 version 16.11.24	16.11.24	2019	1929	192930148	14.29
Visual Studio 2019 version 16.11.27	16.11.27	2019	1929	192930151	14.29
Visual Studio 2019 version 16.11.35	16.11.35	2019	1929	192930154	14.29
Visual Studio 2022 version 17.0.1	17.0.1	2022	1930	193030705	14.30
Visual Studio 2022 version 17.0.2	17.0.2	2022	1930	193030706	14.31
Visual Studio 2022 version 17.1.3	17.1.3	2022	1931	193131105	14.31
Visual Studio 2022 version 17.2.2	17.2.2	2022	1932	193231329	14.32
Visual Studio 2022 version 17.3.4	17.3.4	2022	1933	193331630	14.33
Visual Studio 2022 version 17.4.0	17.4.0	2022	1934	193431933	14.34
Visual Studio 2022 version 17.5.0	17.5.0	2022	1935	193532215	14.35
Visual Studio 2022 version 17.6.0	17.6.0	2022	1936	193632532	14.36
Visual Studio 2022 version 17.6.2	17.6.2	2022	1936	193632532	14.36.32532
Visual Studio 2022 version 17.6.4	17.6.4	2022	1936	193632535	14.36.32532
Visual Studio 2022 version 17.7.0	17.7.0	2022	1937	193732822	14.36.32543
Visual Studio 2022 version 17.8.0	17.8.0	2022	1938	193833130	14.38.33135
Visual Studio 2022 version 17.9.1	17.9.1	2022	1939	193933520	14.39.33520
Visual Studio 2022 version 17.9.6	17.9.6	2022	1939	193933523	14.39.33523

Compatibility

ABI

The Visual C++ compiler ABI have historically changed between major compiler releases. ^[54] This is especially the case for STL containers, where container sizes have varied a lot between compiler releases. ^[55] 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 C ^[56] or COM ^[57] interfaces, which are designed to have a stable ABI between compiler releases.

All 14.x MSVC releases have a stable ABI, ^[58] 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.

C runtime libraries

Visual C++ ships with different versions of C runtime libraries. ^[59] 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. ^[59]

POSIX

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. ^[60] 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.

C

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. ^[61]

Visual C++ 2013 finally added support for various C99 features in its C mode (including designated initializers, compound literals, and the _Bool type), ^[62] though it was still not complete. ^[63] 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. ^[64]

Most of the changes from the C11 revision of the standard were still not supported by Visual C++ 2017. ^[65] For example, generic selections via the _Generic keyword are not supported by the compiler and result in a syntax error. ^[66]

The preprocessor was overhauled in 2018, with C11 in sight: ^[67]

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. ^[68]

In September 2020, Microsoft announced C11 and C17 standards support in MSVC would arrive in version 16.8. ^[69] 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 ^[70] and in version 17.8, support for threads was added, this time not behind a compiler flag. ^{[71] [72]}

C++

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-. ^[73]

References

1. "Visual C++ adds Windows support". InfoWorld. February 22, 1993. p. 17.
2. Lextrait, Vincent (January 2010). "The Programming Languages Beacon, v10.0". Archived from the original on 30 May 2012. Retrieved 14 March 2010.
3. "Do I need these Microsoft Visual C++ redistributables?". Ask Leo!. Retrieved 2012-11-18.
4. Computer Language - Issue 06 (1985-02)(CL Publications)(US). February 1985.
5. Leibson, Steve (1985-02-01). "Software Reviews: Expert team analyzes 21 C compilers". Computer Language. Retrieved 2020-06-05.
6. Ladd, Scott Robert (August 1, 1990). "Optimizing With Microsoft C 6.0".
7. Myers, Ben (1992-07-01). "Microsoft C/C++". PC Magazine . Ziff Davis. p. 387. Retrieved 2023-12-21.
8. "News/Software Pipeline Announced". InfoWorld . InfoWorld Media Group. 1993-03-15. Retrieved 2023-12-21.
9. Retrieved from http://support.microsoft.com/kb/196831.
10. "Visual C++ is a strong development tool". InfoWorld. June 21, 1993. p. 94.
11. "Rival DOS Extenders debut at show". InfoWorld. March 1, 1993. p. 18.
12. "Visual C++ 1.5 integrates OLE, ODBC". InfoWorld. November 8, 1993. p. 5.
13. "Microsoft set to prerelease 32-bit Visual C++". InfoWorld. July 19, 1993. p. 12.
14. "C++ IDEs evolve". InfoWorld. April 4, 1994. p. 79.
15. "Microsoft Visual C++ Strategy".
16. Cullens, Chane; Blackwell, Ken (1995). Cross-Platform Development Using Visual C++. M&T Books. ISBN   1-55851-428-7 . Retrieved 27 January 2024.
17. Plamondon, James (9 October 1997). "Generalized Evangelism Timeline" (PDF). Microsoft Corporation. Retrieved 27 January 2024.
18. "Obsolete Products". Archived from the original on 2005-08-14.
19. Toth, Viktor (1996). "1". Visual C++ 4.0 unleashed. Indianapolis: SAMS Publishing. ISBN   9780672308741 . Retrieved 26 July 2013.
20. "History of Visual Studio (Part 3)". 6 August 2021.
21. "Major Changes from Visual C++ 4.0 to 4.2". Archived from the original on 2010-02-28. Retrieved 2018-04-18.
22. "Major Changes from Visual C++ 4.2 to 5.0".
23. "Microsoft Visual C++ 5.0 Learning Edition". Microsoft . Archived from the original on April 27, 1999.
24. "Microsoft Visual C++ 5.0 Professional Edition". Microsoft . Archived from the original on April 27, 1999.
25. "Microsoft Visual C++ 5.0 Enterprise Edition". Microsoft . Archived from the original on April 17, 1999.
26. "Microsoft Visual C++ 5.0 RISC Edition". Microsoft . Archived from the original on April 29, 1999.
27. Shields, Nathan P. (June 8, 2018). "Criminal Complaint". United States Department of Justice. p. 128. 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.
28. "Major Changes from Visual C++ 5.0 to 6.0". Archived from the original on September 14, 2008.
29. 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.
30. Douglas Boling :Programming Microsoft Windows CE .NET, Third Edition Microsoft Press; 3rd edition (June 25, 2003) Paperback: 1264 pages ISBN   978-0735618848 - Companion CD with Microsoft eMbedded Visual C++ 4.0 Service Pack 2 Archived 2013-02-11 at archive.today
31. How to: Modify WINVER and _WIN32_WINNT
32. Breaking Changes
33. Windows Platforms (CRT)
34. "Visual C++ 2008 Breaking Changes". 25 May 2023.
35. Visual C++ Team Blog. "IntelliSense, part 2: The Future" . Retrieved March 12, 2008.
36. "Why IntelliSense is not supported for C++/CLI in Visual Studio 2010" . Retrieved March 13, 2011.
37. Visual C++ Team Blog (27 May 2009). "Rebuilding Intellisense".
38. Visual C++ Team Blog. "Visual C++ Code Generation in Visual Studio 2010".
39. "C++0x Core Language Features In VC10: The Table".
40. "Stephan T. Lavavej: Everything you ever wanted to know about nullptr".
41. Microsoft Windows SDK Blog. "Released: Windows SDK for Windows 7 and .NET Framework 4".
42. 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
43. "What's New for Visual C++ in Visual Studio 2012". Microsoft Developer Network . Microsoft. 29 November 2012. Retrieved September 20, 2015.
44. "What's New for Visual C++ in Visual Studio 2013". Microsoft Developer Network . Microsoft. 28 April 2015. Retrieved September 20, 2015.
45. Eric Battalio (July 20, 2015). "Visual Studio 2015 RTM Now Available". Visual C++ Team Blog. Microsoft.
46. Stephan T. Lavavej (June 19, 2015). "C++11/14/17 Features In VS 2015 RTM". Visual C++ Team Blog. Microsoft.
47. Reviewing Microsoft's Automatic Insertion of Telemetry into C++ Binaries
48. "Visual Studio adding telemetry function calls to binary? • /r/cpp". reddit. 7 May 2016. Retrieved 2016-08-17.
49. Julia Liuson (March 7, 2017). "Announcing Visual Studio 2017 General Availability… and more". Visual Studio Team Blog. Microsoft.
50. Amanda Silver (February 14, 2019). "Join us April 2nd for the Launch of Visual Studio 2019!". Visual Studio Team Blog. Microsoft.
51. Amanda Silver (November 8, 2021). "Visual Studio 2022 now available". Visual Studio Team Blog. Microsoft.
52. "Pre-defined Compiler Macros / Wiki / Compilers". dev.to. 22 May 2018. Retrieved 2023-02-20.
53. "Predefined Macros / Microsoft Learn". learn.microsoft.com. 8 August 2022. Retrieved 2023-05-26.
54. Microsoft MSDN: Breaking Changes in Visual C++
55. Microsoft MSDN: Containers (Modern C++)
56. Microsoft MSDN: Portability At ABI Boundaries (Modern C++)
57. Microsoft forum: Binary compatibility across Visual C++ versions Archived 2013-02-16 at archive.today
58. docs.microsoft.com: C++ binary compatibility between Visual Studio 2015, 2017, and 2019
59. C Run-Time Libraries
60. "Compatibility". Microsoft: CRT library features. 26 October 2022.
61. "C99 support". Microsoft Connect. Archived from the original on 2016-03-04. Retrieved 2015-09-21.
62. "What's New for Visual C++ in Visual Studio 2013". Microsoft Developer Network. Microsoft. 28 April 2015.
63. Pat Brenner (July 19, 2013). "C99 library support in Visual Studio 2013". Visual C++ Team Blog. Microsoft.
64. "What's New for Visual C++ in Visual Studio 2015". Microsoft Developer Network. Microsoft. 3 January 2018.
65. "Walkthrough: Compile a C program on the command line". Visual C++ Documentation. Microsoft. 10 May 2022.
66. "MSVC 2017 does not support _Generic (type generic macros) in C".
67. Luvsanbat, Bat-Ulzii (July 6, 2018). "MSVC Preprocessor Progress towards Conformance". Microsoft Developer Network . Archived from the original on 3 Mar 2024.
68. "C++20 Features and Fixes". reddit . July 3, 2020.
69. "C11 and C17 Standard Support Arriving in MSVC". September 14, 2020.
70. "C11 Atomics in Visual Studio 2022 version 17.5 Preview 2". 2022-12-13.
71. "C11 Threads in Visual Studio 2022 version 17.8 Preview 2". 2023-09-26.
72. Murphy, Adrian (2023-11-14). "Visual Studio 17.8 now available!". Visual Studio Blog. Retrieved 2024-01-12.
73. "Two-phase name lookup support comes to MSVC". 2017-09-11.

Further reading

• Johnson, Brian (8 August 2004). "Building Win32 Applications Using Visual C++ 2005 Express". Brian Johnson's Startup Developer Blog. Microsoft – via Microsoft Docs Archive.
• Springfield, Jim (25 September 2015). "Rejuvenating the Microsoft C/C++ Compiler". C++ Team Blog. Microsoft.

External links

• Official website
• C++ Tools and Features in Visual Studio Editions
• Microsoft C++ Build Tools
• C9::GoingNative on Microsoft Channel 9