For all you folks who still have to write apps with MSVS ....
Before I retired, over a year ago, I was using MS Visual Studio 2003 at work to compile apps built with Qt4. I heard that my replacement recently upgraded to version 2005. Now he is between a rock an a hard place.
If he doesn't patch MSVS 2005 with the KB971090 security patch he risks malware exposure. If he does, client PCs won't be able to run his executable.
http://www.ives.fr/index.php/blog/post/19
Of the four solutions proposed it seems the only one that works is to remove KB971090.
To make matters worse:
I'm wondering.... is it "security" or is Microsoft trying to force developers, and hence users, to "upgrade" to Win7?
Before I retired, over a year ago, I was using MS Visual Studio 2003 at work to compile apps built with Qt4. I heard that my replacement recently upgraded to version 2005. Now he is between a rock an a hard place.
If he doesn't patch MSVS 2005 with the KB971090 security patch he risks malware exposure. If he does, client PCs won't be able to run his executable.
http://www.ives.fr/index.php/blog/post/19
Of the four solutions proposed it seems the only one that works is to remove KB971090.
To make matters worse:
We also noticed that some client PCs running Windows Vista had updated build 3053 (not 4053) and when we tried to ship build 4053 as private assembly, Windows complained that the two assemblies were in conflict (although we were shipping the MFC and CRT as private assemblies). This conflict message was so undocumented that nobody seems to have encountered the situation. So the simplest solution was to remove this security fix.
I am not sure this is sustainable when Windows 7 will start to be around ...
I am not sure this is sustainable when Windows 7 will start to be around ...
Remember, it was the same M$ who argued that Internet Explorer "couldn't be separated" from Windoze, yet, they ultimately did.
Comment