<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Good post on running/writing/compiling managed binaries as 32-bit or 64-bit</title><link>http://blogs.msdn.com/grantri/archive/2004/10/15/243036.aspx</link><description>How the OS Loader will force .Net v1.0/1.1 executables to run under WOW64 on a 64-Bit Machine (http://blogs.msdn.com/joshwil/archive/2004/10/15/243019.aspx) In General I think all of Josh's recent posts are worth a read. --Grant</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Good post on running/writing/compiling managed binaries as 32-bit or 64-bit</title><link>http://blogs.msdn.com/grantri/archive/2004/10/15/243036.aspx#244085</link><pubDate>Mon, 18 Oct 2004 19:15:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:244085</guid><dc:creator>Ryan Lamansky (Kardax)</dc:creator><description>Very interesting stuff, and I like the direction that you're taking with this.&lt;br&gt;&lt;br&gt;Since the move to .NET 2.0 on 64-bit is something the developer has to force, and the developer -must- be ready for problems, it seems to be a good time to introduce some of those hotly-debated performance enhancements mentioned around here.  ( &lt;a target="_new" href="http://blogs.msdn.com/grantri/archive/2004/09/07/226355.aspx"&gt;http://blogs.msdn.com/grantri/archive/2004/09/07/226355.aspx&lt;/a&gt; )</description></item></channel></rss>