News for hackers. Stuff that matters.
Re:Windows is not a Microsoft Visual C/C++ Run-Time delivery... by Aardwolf on Saturday April 12, 2014 @06:29AM (#7577501)
Why does a program compiled with VS need a specific DLL anyway?

Can't VS compile FOR Windows, with only the DLLs Windows provides by default?

Re:Windows is not a Microsoft Visual C/C++ Run-Time delivery... by ygra on Saturday April 12, 2014 @06:38AM (#7577512)
Sure, just don't link against the C++ runtime library and you're good. Of course, you won't have anything said runtime lib provides, then. Or link the runtime statically, as suggested in a few other posts. Your binary size will increase then, though.
Re:Windows is not a Microsoft Visual C/C++ Run-Time delivery... by to3m on Saturday April 12, 2014 @08:55AM (#7577718)
Here's an article about it: http://www.drdobbs.com/avoiding-the-visual-c-runtime-library...

Without the runtime library, strictly speaking you're no longer programming C or C++, hence the surprises...

Re:Windows is not a Microsoft Visual C/C++ Run-Time delivery... by maxerickson on Saturday April 12, 2014 @08:48AM (#7577704)
That's what the article is about, why they decided to not have VS link against the OS runtime.

At some point, the decision was made to just give up and declare it an operating system DLL, to be used only by operating system components.

Makes it clear enough that it was a choice they made, with the big reason being the effort required to maintain compatibility across so many systems and compilers. My knowledge of it never really got past the poking-with-a-stick stage, but apparently (at least some of) the windows SDK compilers were able to link to the system runtime well after they made the switch in VS.