Visual C++ Microsoft
Repository Issues Documentation Code Samples Offline Installers
- Visual C++ Microsoft Download
- C++ Download Windows 10
- Visual C++ Microsoft 2008
- Microsoft Visual C++ 2010 Redistributable X86
The C/C++ extension adds language support for C/C++ to Visual Studio Code, including features such as IntelliSense and debugging.
Overview and tutorials
C/C++ extension tutorials per compiler and platform
Quick links
Dec 30, 2014 Visual C Redistributable Packages for Visual Studio 2013 Important! Selecting a language below will dynamically change the complete page content to that language. Download Visual Studio Community, Professional, and Enterprise. Try Visual Studio IDE, Code or Mac for free today. The Microsoft C/C for Visual Studio Code extension supports IntelliSense, debugging, code formatting, auto-completion. Visual Studio for Mac doesn't support Microsoft C, but does support.NET languages and cross-platform development. For installation instructions, see Install Visual Studio for Mac.
Questions and feedback
FAQs
Check out the FAQs before filing a question.
Provide feedback
File questions, issues, or feature requests for the extension.
Known issues
If someone has already filed an issue that encompasses your feedback, please leave a 👍 or 👎 reaction on the issue to upvote or downvote it to help us prioritize the issue.
Quick survey
Let us know what you think of the extension by taking the quick survey.
Offline installation
The extension has platform-specific binary dependencies, therefore installation via the Marketplace requires an Internet connection in order to download additional dependencies. If you are working on a computer that does not have access to the Internet or is behind a strict firewall, you may need to use our platform-specific packages and install them by running VS Code's 'Install from VSIX...' command. These 'offline' packages are available at: https://github.com/Microsoft/vscode-cpptools/releases.
| Package | Platform |
|---|---|
cpptools-linux.vsix | Linux 64-bit |
cpptools-linux-armhf.vsix | Linux ARM 32-bit |
cpptools-linux-aarch64.vsix | Linux ARM 64-bit |
cpptools-osx.vsix | macOS 64-bit |
cpptools-osx-arm64.vsix | macOS ARM64 |
cpptools-win32.vsix | Windows 64-bit & 32-bit |
cpptools-win-arm64.vsix | Windows ARM64 |
cpptools-linux32.vsix | Linux 32-bit (available up to version 0.27.0) |
Contribution
Contributions are always welcome. Please see our contributing guide for more details.
Microsoft Open Source Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
Data and telemetry
This extension collects usage data and sends it to Microsoft to help improve our products and services. Collection of telemetry is controlled via the same setting provided by Visual Studio Code: 'telemetry.enableTelemetry'. Read our privacy statement to learn more.
This article describes how to redistribute the shared C runtime component in Visual C++.
Visual C++ Microsoft Download
Original product version: Visual Studio, .NET Framework
Original KB number: 326922
Summary
When you build an application in Microsoft Visual Studio, and the application uses the C run-time libraries (CRT), distribute the appropriate CRT dynamic link library (DLL) from the following list with your application:
- Msvcr90.dll for Microsoft Visual C++ 2008
- Msvcr80.dll for Microsoft Visual C++ 2005
- Msvcr71.dll for Microsoft Visual C++ .NET 2003 with the Microsoft .NET Framework 1.1
- Msvcr70.dll for Microsoft Visual C++ .NET 2002 with the Microsoft .NET Framework 1.0
For Msvcr70.dll or for Msvcr71.dll, you should install the CRT DLL into your application program files directory. You may not install these files into the Windows system directories. For Msvcr80.dll and for Msvcr90.dll, you should install the CRT as Windows side-by-side assemblies.
DLL conflict
The shared CRT DLL has been distributed by Microsoft in the past as a shared system component. It may cause problems when you run applications that are linked to a different version of the CRT on computers that don't have the correct versions of the CRT DLL installed. It's commonly referred to as the DLL Conflict problem.
To address this issue, the CRT DLL is no longer considered a system file, so distributing the CRT DLL with any application that relies on it. Because it's no longer a system component, install it in your applications Program Files directory with other application-specific code. Which prevents your application from using other versions of the CRT library that may be installed on the system paths.
Visual C++ .NET 2003 or Visual C++ .NET 2002 installs the CRT DLL in the System32 directory on a development system. Which is installed as a convenience for the developer. Otherwise, all projects that are built with Visual C++ that link with the shared CRT require a copy of the DLL in the build directory for debugging and execution. Visual C++ 2005 and Visual C++ 2008 install the CRT DLL as a Windows side-by-side assembly on Windows XP and later operating systems. Windows 2000 doesn't support side-by-side assemblies. On Windows 2000, the CRT DLL is installed in the System32 directory.
When you distribute applications that require the Shared CRT library in the CRT DLL, we recommend that you use the CRT.msm merge module, which is included with Visual C++ instead of directly distributing the DLL file.
Windows side-by-side assemblies
C++ Download Windows 10
Visual C++ Microsoft 2008
Msvcr80.dll with Visual C++ 2005 and Msvcr90.dll with Visual C++ 2008 are redistributed as Windows side-by-side assemblies except on Windows 2000. You can install these versions of the CRT on target computers by running the Vcredist_x86.exe application that is included with Visual Studio. There are installers for the x64 and IA-64 platforms also. Instead, you can use the CRT msm merge module, which is supplied with Visual Studio to package the CRT installer into your own setup application. Which will make the CRT available as a shared assembly to all applications because it's installed in the windowswinsxs directory on supported operating systems.