The MFC version that ships with Visual Studio 2010 is known to cause major explosions in file size when you link statically. To avoid that problem, I use the Visual Studio 2008 build tools for such cases. I recently got quite a surprise when I rebuilt one such MFC application and discovered that the executable had ballooned from 400kb to 2MB in the space of one week despite only very minor changes. ...
I have more or less completed the task of migrating my internal projects to Visual Studio 2010. Native C++ programmers are pretty low on the totem pole of programming coolness these days, but Microsoft did throw us a few bones. At this point I have to say I’m ambivalent overall with VS 2010, but I really like some of the architectural changes and I’m excited about the future. ...
[Update: See Visual Studio 2010 Native Multi-Targeting] Developers, if you use VC Build Hook and/or need the same capability in Visual Studio 2010, please let Microsoft know by voting for a fix. I’ve written before (and here) about the problem. I think it is possible to hack a third party solution, but by far the best solution is for Microsoft to add back the ability to produce ANSI response files in service pack 1.
No, Microsoft didn’t really try to patent photons, but check out the the ironic twists described in this account of a recent US Supreme Court hearing. Here’s a summary (exaggerated a bit for effect): 1. Microsoft argues that software is not patentable, therefore it is not guilty of patent infringement. 2. The US Government argues on Microsoft’s behalf that software is patentable, but photons are not.