Most compilers used by app developers don't use this, but...
link /dump /exports c:\windows\system32\msvcrt.dll
Dump of file c:\windows\system32\msvcrt.dll
Section contains the following exports for msvcrt.dll
00000000 characteristics
57898F96 time date stamp Fri Jul 15 18:36:22 2016
0.00 version
1 ordinal base
1317 number of functions
1317 number of names
ordinal hint RVA name
....
1160 487 00019DE0 malloc
....
1183 49E 00048940 printfMost compilers used by app developers don't use that for good reason: Microsoft says that it is an unsupported, undocumented library which is off limits to application developers. Programs that are part of Windows itself use it.
https://blogs.msdn.microsoft.com/oldnewthing/20140411-00/?p=...
The run-time libraries on top of this aren't part of the system. Each application brings its own and so of course hell will break loose if you mix and match.
Windows has no malloc or printf (not for public use anyway).
In the POSIX world, the user-space C run-time support is part of the platform so it is carefully versioned, just like kernel32.dll on Windows.
User space compiler run-time support isn't part of the platform on Windows; it is not that carefully versioned. Everyone is supposed to provide their own. If you have a compiler from Acme, Inc, you use the Acme C library with Acme malloc and Acme printf.
> putting DLLs into a dedicated folder
Which actually works on Windows, that's the thing.
Searching for shared libs in the same directory as the executable is very nice: like me.c finding its #include "me.h" next to it.
The Unix people didn't pay attention to their own programming language when they designed shared libs.