Can I download the Visual C++ Command Line Compiler without Visual Studio?

by

As said, there is no way to do that. You need to download the entire 4-6GB+ bundle. MS deployment is a botch.

There is no need, however, to actually install everything. If you’re up to some manual installation, you can extract individual components from the bundle and put them all in a more organized directory tree.

For example, I’ve found the following set to be the bare minimum needed for using the current MSVC2013 compilers in a x86 environment:

  • vc_compilerCore86.msi: MSVC toolchain;
  • vc_compilerCore86res.msi: MSVC toolchain MUI resources;
  • vc_librarycore86.msi: MSVC library stuff;
  • vc_LibraryDesktopX86.msi: More MSVC library stuff;
  • Windows Software Development Kit for Windows Store Apps-x86_en-us.msi: Windows SDK files and related tools (rc.exe, mt.exe, etc.);
  • Windows Software Development Kit-x86_en-us.msi: More Windows SDK files (specifically, WinSock2.h, WS2_32.lib, maybe others).

Remember that you can extract the contents of a MSI file by running msiexec /a <msifile> TARGETDIR="<path>" (jot a /quiet parameter if you’re batching). Of course, you can also put more into your package by investigating the MSI files inside the bundle. In particular, the above set is missing the latest MSBuild tools, since I don’t care for them. Stuff is often scattered around between multiple MSIs cluelessly, so good luck.

I’ve got a 50MB (!!!) 7z-file containing this set for local deployment, though I cannot share this publicly due to Microsoft licensing restrictions.

UPDATE:

This is the list of MSI files for MSVC2015 tools, headers and libraries:

packages\VisualC_D14\VC_Tools.Core\VC_Tools.Core.msi
packages\VisualC_D14\VC_Tools.Core.Res\VC_Tools.Core.Res.msi
packages\VisualC_D14\VC_Tools.X86.Base\VC_Tools.X86.Base.msi
packages\VisualC_D14\VC_Tools.X86.Base.Res\VC_Tools.X86.Base.Res.msi
packages\VisualC_D14\VC_Tools.X86.Nat\VC_Tools.X86.Nat.msi
packages\VisualC_D14\VC_Tools.X86.Nat.Res\VC_Tools.X86.Nat.Res.msi
packages\VisualC_D14\VC_Tools.X86.X64\VC_Tools.X86.X64.msi
packages\VisualC_D14\VC_Tools.X86.X64.Res\VC_Tools.X86.X64.Res.msi
packages\VisualC_D14\VC_PremTools.X86.Base\VC_PremTools.X86.Base.msi
packages\VisualC_D14\VC_PremTools.X86.Base.Res\VC_PremTools.X86.Base.Res.msi
packages\VisualC_D14\VC_PremTools.X86.Nat\VC_PremTools.X86.Nat.msi
packages\VisualC_D14\VC_PremTools.X86.Nat.Res\VC_PremTools.X86.Nat.Res.msi
packages\VisualC_D14\VC_PremTools.X86.X64\VC_PremTools.X86.X64.msi
packages\VisualC_D14\VC_PremTools.X86.X64.Res\VC_PremTools.X86.X64.Res.msi
packages\VisualC_D14\VC_CRT.Headers\VC_CRT.Headers.msi
packages\VisualC_D14\VC_CRT.X86.Desktop\VC_CRT.X86.Desktop.msi
packages\VisualC_D14\VC_CRT.X86.Store\VC_CRT.X86.Store.msi
packages\VisualC_D14\VC_CRT.X64.Desktop\VC_CRT.X64.Desktop.msi
packages\VisualC_D14\VC_CRT.X64.Store\VC_CRT.X64.Store.msi
packages\VisualC_D14\VC_CRT.Redist.Res\VC_CRT.Redist.Res.msi
packages\VisualC_D14\VC_CRT.Redist.X86\VC_CRT.Redist.X86.msi
packages\VisualC_D14\VC_CRT.Redist.X64\VC_CRT.Redist.X64.msi
packages\VisualC_D14\VC_ATL.Headers\VC_ATL.Headers.msi
packages\VisualC_D14\VC_ATL.X86\VC_ATL.X86.msi
packages\VisualC_D14\VC_ATL.X64\VC_ATL.X64.msi
packages\VisualC_D14\VC_MFC.Headers\VC_MFC.Headers.msi
packages\VisualC_D14\VC_MFC.X86\VC_MFC.X86.msi
packages\VisualC_D14\VC_MFC.X64\VC_MFC.X64.msi
packages\VisualC_D14\VC_PGO.Headers\VC_PGO.Headers.msi
packages\VisualC_D14\VC_PGO.X86\VC_PGO.X86.msi
packages\VisualC_D14\VC_PGO.X64\VC_PGO.X64.msi
packages\Win10_UniversalCRTSDK\Universal CRT Headers Libraries and Sources-x86_en-us.msi

And this is the list of MSI files for WinSDK10 tools, headers and libraries (downloaded separately):

Installers\Windows SDK Desktop Headers Libs Metadata-x86_en-us.msi
Installers\Windows SDK Desktop Tools-x86_en-us.msi
Installers\Windows SDK for Windows Store Apps Headers Libs-x86_en-us.msi
Installers\Windows SDK for Windows Store Apps Tools-x86_en-us.msi

All of this include stuff for both x86 and x64 (I haven’t considered ARM or IA64). Both bundles compressed with LZMA will yield a 185MB file.

More Related Contents:

  1. c++ vectors causing break in my game [closed]
  2. What are the different calling conventions in C/C++ and what do each mean?
  3. CreateProcess from memory buffer
  4. C++ #include is not found
  5. How to create a process in C++ on Windows?
  6. Win32: Bring a window to top
  7. Title Name not showing and background color not changing
  8. How to get main window handle from process id?
  9. Convert CString to const char*
  10. Can I use CreateFile, but force the handle into a std::ofstream?
  11. What does the operation c=a+++b mean?
  12. How would I load a PNG image using Win32/GDI (no GDI+ if possible)?
  13. Is using #pragma warning push/pop the right way to temporarily alter warning level?
  14. Will C++ exceptions safely propagate through C code?
  15. How to export a C++ class from a dll? [duplicate]
  16. How can I get the path of a Windows “special folder” for a specific user?
  17. C++ Executing CMD Commands
  18. How to validate numeric input in C++
  19. Why does this program crash: passing of std::string between DLLs
  20. What is the difference between the /Ox and /O2 compiler options?
  21. How to enforce the ‘override’ keyword?
  22. C++ Memory Barriers for Atomics
  23. Win32: How to hide 3rd party windows in taskbar by hWnd
  24. Explicitly initialize DWORD to 1, but debugger shows wildly out of range value
  25. Disabling Warnings generated via _CRT_SECURE_NO_DEPRECATE
  26. std::thread::join() hangs if called after main() exits when using VS2012 RC
  27. converting narrow string to wide string
  28. How can I enumerate/list all installed applications in Windows XP?
  29. DoEvents equivalent for C++?
  30. Why can’t Visual Studio find my DLL? [duplicate]

Leave a Comment