New
#1
11 Instances of Microsoft C++
Is this a case of MS being sloppy or do I really need 11 instances?
11 Instances of Microsoft C++
-
-
New #2
When you consider that most of them showing in Programs and Features weren't even installed by Microsoft in the first place, no. For example,
You can start removing them if you wish, but don't be surprised if things stop working.
-
New #3
You probably don't need all of them, but since they're linked to a .dll, the programs that require them might crash if you remove them. It's recommended that you leave them.
-
New #4
-
New #5
I remember this from VC++ 6.0 that the default setting on the compiler is to use a run-time dll instead of compiling stand-alone. I have Visual C++ 2010 Express and it's still the same. Instead of changing the compile switch to compile a stand-alone exe a lot of developers seem to feel the need to just include the run-time dll in the install package. I don't really understand with PCs coming off the shelf with 8 GB ram why they feel compelled to compile with a run-time dll as the default. Inertia I suppose. Every time I set up the compiler on a new machine, then run the .exe on a machine without VC++ installed I get the missing dll error msg, and have to go change the default for all my projects.
Nothing ever seems to really change.
-
New #6
Dueling dlls
Dueling C++
The more things change, the more they stay the same.
-
New #7
Heh heh. Like now everyone keeps telling me "you really don't have to program in 64 bit. In fact it may be wasteful of memory in some sittuations ... blah blah" All the same stuff they said when people clamored for 32 bit support. Just substitute "64" for every instance of "32" bitness. :)
Quote
Related Discussions