Size of executable doubles since Windows Update on April 14, 2011
-
My Configuration is VS2008 MFC statically linked app. I have been compiling my app over a 1000 times and am intune with the size of the exe. It has slightly more than doubled in size as of this week ever since the windows update on April 14. For the time being I am compiling at my alternate computer that has "Automatic Windows Update" turned off and get the usual size of the executable. Has anyone else observed this. I have compiled other projects and have noticed the same pattern - exe doubles in size. :|
-
My Configuration is VS2008 MFC statically linked app. I have been compiling my app over a 1000 times and am intune with the size of the exe. It has slightly more than doubled in size as of this week ever since the windows update on April 14. For the time being I am compiling at my alternate computer that has "Automatic Windows Update" turned off and get the usual size of the executable. Has anyone else observed this. I have compiled other projects and have noticed the same pattern - exe doubles in size. :|
-
try turning the MAP file on as a link option, on both machines and compare the output is this release or debug?
Thank you for responding barnyman. This is a release build (both of them). Since reporting the problem I have some additional information. I ran both executables (the big and the small one) on the same computer and used the ProcessMonitor tool to determine and compare the dll's that each was loading. The results show the larger exe is loading 4 additional dll's. They are: dwmapi.dll msimg32.dll winmm.dll gdiplus.dll I am not using any code the needs these dll's. In my projects settings: Linker->Input->Ignore Specific Libray settings, I blocked all of the lib files that depend on these dll's and can't compile the project. This tells me there is some new dependency that has formed. In searching the Internet I learned that programmers that have moved to VS2010 are having the same problem. It seems there are some MFC files that have some built in dependencies to the MFC feature pack even though their project is not using them. I suspect that is what is going on with my project even though I am still using VS2008. The most latest Windows update made that happen. (I have used the MFC feature pack in some other projects but don't do that anymore. I can do it all without it.) This experience gives new meaning to the concept of VC_EXTRALEAN and dare I say WIN32_LEAN_AND_MEAN from back in the day. More to come. Once again thanks for your time barneyman. Art
-
Thank you for responding barnyman. This is a release build (both of them). Since reporting the problem I have some additional information. I ran both executables (the big and the small one) on the same computer and used the ProcessMonitor tool to determine and compare the dll's that each was loading. The results show the larger exe is loading 4 additional dll's. They are: dwmapi.dll msimg32.dll winmm.dll gdiplus.dll I am not using any code the needs these dll's. In my projects settings: Linker->Input->Ignore Specific Libray settings, I blocked all of the lib files that depend on these dll's and can't compile the project. This tells me there is some new dependency that has formed. In searching the Internet I learned that programmers that have moved to VS2010 are having the same problem. It seems there are some MFC files that have some built in dependencies to the MFC feature pack even though their project is not using them. I suspect that is what is going on with my project even though I am still using VS2008. The most latest Windows update made that happen. (I have used the MFC feature pack in some other projects but don't do that anymore. I can do it all without it.) This experience gives new meaning to the concept of VC_EXTRALEAN and dare I say WIN32_LEAN_AND_MEAN from back in the day. More to come. Once again thanks for your time barneyman. Art
-
-
The problem has been fixed with the recent June 15, 2011 Windows update. Back to normal. What a relief!