<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>.NET Framework Installer Technologies: A Primer</title><link>http://blogs.technet.com/blairn/archive/2005/11/01/NetFX-InstallerTechnologyPrimer.aspx</link><description>Updates for the the .NET Framework 1.1 come in two flavors: One set of packages for 32-bit x86 versions of Windows Server 2003 and a different package for everything else. Similarly, updates for the .NET Framework 1.0 come in two flavors as well: One</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>How to install and update the .NET Framework 1.1 on different operating systems</title><link>http://blogs.technet.com/blairn/archive/2005/11/01/NetFX-InstallerTechnologyPrimer.aspx#426334</link><pubDate>Tue, 25 Apr 2006 23:23:18 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:426334</guid><dc:creator>Update Deployment for Visual Studio and the .NET Framework</dc:creator><description>I've blogged previously about how confusing our servicing story is for .NET Framework 1.1 on Windows Server 2003 and 64-bit versions of Windows XP and Windows Server 2003. Now there's a new KB article in the Microsoft Knowledge Base to help customers</description></item></channel></rss>