<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Microsoft on ManuSoft</title><link>https://www.manusoft.com/tags/microsoft/</link><description>Recent content in Microsoft on ManuSoft</description><generator>Hugo</generator><language>en-us</language><copyright>1991–2026</copyright><lastBuildDate>Fri, 15 Apr 2011 17:24:46 +0000</lastBuildDate><atom:link href="https://www.manusoft.com/tags/microsoft/index.xml" rel="self" type="application/rss+xml"/><item><title>The MFC Balloon</title><link>https://www.manusoft.com/archive/blog/the-mfc-balloon/</link><pubDate>Fri, 15 Apr 2011 17:24:46 +0000</pubDate><guid>https://www.manusoft.com/archive/blog/the-mfc-balloon/</guid><description>&lt;p&gt;The MFC version that ships with Visual Studio 2010 is known to cause &lt;a href="https://connect.microsoft.com/VisualStudio/feedback/details/504714/statically-linked-mfc-applications-are-massive"&gt;major explosions in file size&lt;/a&gt; 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.&lt;/p&gt;</description></item><item><title>Visual Studio 2010 Migration Post Mortem</title><link>https://www.manusoft.com/archive/blog/visual-studio-2010-migration-post-mortem/</link><pubDate>Mon, 18 Oct 2010 23:49:22 +0000</pubDate><guid>https://www.manusoft.com/archive/blog/visual-studio-2010-migration-post-mortem/</guid><description>&lt;p&gt;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&amp;rsquo;m ambivalent overall with VS 2010, but I really like some of the architectural changes and I&amp;rsquo;m excited about the future.&lt;/p&gt;</description></item><item><title>Using VC 7 build tools in Visual Studio 2010</title><link>https://www.manusoft.com/archive/blog/using-vc-7-build-tools-in-visual-studio-2010/</link><pubDate>Thu, 24 Jun 2010 16:13:38 +0000</pubDate><guid>https://www.manusoft.com/archive/blog/using-vc-7-build-tools-in-visual-studio-2010/</guid><description>&lt;p&gt;&lt;em&gt;[Update: See &lt;/em&gt;&lt;a href="http://otb.manusoft.com/2010/10/visual-studio-2010-native-multi-targeting.htm"&gt;&lt;em&gt;Visual Studio 2010 Native Multi-Targeting&lt;/em&gt;&lt;/a&gt;&lt;em&gt;]&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Developers, if you use &lt;a href="http://www.manusoft.com/resources/arxtips/vcbuildhook.html"&gt;VC Build Hook&lt;/a&gt; and/or need the same capability in Visual Studio 2010, please let Microsoft know by &lt;a href="https://connect.microsoft.com/VisualStudio/feedback/details/570466/vs-2010-native-build-cannot-produce-ansi-response-files"&gt;voting for a fix&lt;/a&gt;. I&amp;rsquo;ve &lt;a href="http://otb.manusoft.com/2010/01/visual-studio-2010-and-vc-build-hook.htm"&gt;written before&lt;/a&gt; (and &lt;a href="http://otb.manusoft.com/2010/04/visual-studio-2010-ships.htm"&gt;here&lt;/a&gt;) 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.&lt;/p&gt;</description></item><item><title>This Just In: Microsoft Patents Photons</title><link>https://www.manusoft.com/archive/blog/this-just-in-microsoft-patents-photons/</link><pubDate>Fri, 02 Mar 2007 17:26:00 +0000</pubDate><guid>https://www.manusoft.com/archive/blog/this-just-in-microsoft-patents-photons/</guid><description>&lt;p&gt;No, Microsoft didn&amp;rsquo;t really try to patent photons, but check out the the ironic twists described in &lt;a href="http://www.betanews.com/article/Supreme_Court_Debates_Patentability_of_Software/1172097039"&gt;this account&lt;/a&gt; of a recent US Supreme Court hearing. Here&amp;rsquo;s a summary (exaggerated a bit for effect):&lt;br /&gt;1. Microsoft argues that software is not patentable, therefore it is not guilty of patent infringement.&lt;br /&gt;2. The US Government argues on Microsoft&amp;rsquo;s behalf that software is patentable, but photons are not.&lt;/p&gt;</description></item></channel></rss>