<?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>Update Deployment for Visual Studio and the .NET Framework : Work in Progress</title><link>http://blogs.technet.com/blairn/archive/tags/Work+in+Progress/default.aspx</link><description>Tags: Work in Progress</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>.NET Framework 1.1 Servicing Releases on Windows Update for 64-bit Systems</title><link>http://blogs.technet.com/blairn/archive/2006/03/28/NetFX1164Annc.aspx</link><pubDate>Wed, 29 Mar 2006 01:35:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423449</guid><dc:creator>blairn</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.technet.com/blairn/comments/423449.aspx</comments><wfw:commentRss>http://blogs.technet.com/blairn/commentrss.aspx?PostID=423449</wfw:commentRss><description>&lt;P&gt;Among the most confusing stories that we have asked&amp;nbsp;.NET Framework&amp;nbsp;customers to understand has been .NET Framework 1.1 support on Windows Server 2003 and 64-bit versions of Windows. I've blogged about this &lt;A href="http://http://blogs.technet.com/blairn/archive/2005/11/01/NetFX_InstallerTechnologyPrimer.aspx"&gt;before&lt;/A&gt;. Today I get to tell you that we've done right by putting .NET Framework 1.1 servicing releases on Windows Update for 64-bit platforms.&lt;/P&gt;
&lt;P&gt;Microsoft releases security updates on the second Tuesday of every month and Windows Update releases non-security updates&amp;nbsp;on the fourth Tuesday of every month.&amp;nbsp; Well, today is the fourth Tuesday in March and we went live with .NET Framework 1.1 Service Pack 1 on Windows Update for supported 64-bit versions of Windows.&lt;/P&gt;
&lt;P&gt;None of these are new releases; they are the exact same binaries that are already on Windows Update for .NET Framework 1.1 running on 32-bit Windows&amp;nbsp;operating systems and have always been available for supported&amp;nbsp;64-bit Windows operating systems on Download Center.&amp;nbsp; What's new is that now if you have .NET Framework 1.1 installed on your x64 or supported Itanium version of Windows then you can keep that .NET Framework 1.1 installation up-to-date using Windows Update, SUS, and WSUS.&lt;/P&gt;
&lt;P&gt;It should be noted that there do exist performance issues running .NET Framework 1.1 on Itanium-based systems (&lt;A href="http://technet2.microsoft.com/WindowsServer/en/Library/2a9b3222-4b2d-4537-a382-9bbb36b2fbc31033.mspx"&gt;here&lt;/A&gt;).&amp;nbsp; There is also a known compatibility issue between ASP.NET 1.1 (a component of&amp;nbsp;the .NET Framework 1.1) and IIS 6.0 on 64-bit versions of Windows (&lt;A href="http://support.microsoft.com/?id=894435"&gt;here&lt;/A&gt;).&amp;nbsp; These are known issues and the current announcement does nothing to mitigate these concerns.&amp;nbsp; Rather, we assume that if you have the .NET Framework 1.1 on&amp;nbsp;a 64-bit Windows system&amp;nbsp;then you have already evaluated and addressed these concerns for your environment.&lt;/P&gt;
&lt;P&gt;The supported operating systems are the following:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Windows XP Professional x64 edition 
&lt;LI&gt;Windows Server 2003 x64 editions 
&lt;LI&gt;Windows Server 2003 for Itanium-based systems w/ Service Pack 1&lt;/LI&gt;&lt;/UL&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=423449" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/blairn/archive/tags/Known+Issues/default.aspx">Known Issues</category><category domain="http://blogs.technet.com/blairn/archive/tags/Work+in+Progress/default.aspx">Work in Progress</category><category domain="http://blogs.technet.com/blairn/archive/tags/Dimensions+of+Deployment/default.aspx">Dimensions of Deployment</category></item><item><title>Deployment Channels</title><link>http://blogs.technet.com/blairn/archive/2005/11/29/DeploymentChannels.aspx</link><pubDate>Wed, 30 Nov 2005 05:26:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:415303</guid><dc:creator>blairn</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/blairn/comments/415303.aspx</comments><wfw:commentRss>http://blogs.technet.com/blairn/commentrss.aspx?PostID=415303</wfw:commentRss><description>&lt;P&gt;I stated in an earlier post that "I am the person in charge of getting product&amp;nbsp;updates (service packs and hotfixes)&amp;nbsp;for Visual Studio and the .NET Framework into distribution channels like Windows Update, Microsoft Update, and the Microsoft Download Center."&amp;nbsp; It occured to me that some of you might care which updates go where.&amp;nbsp; If you do, read on!&lt;/P&gt;
&lt;P&gt;In a nutshell, updates to the .NET Framework go on Windows Update while updates for everything else (in this case, Visual Studio)&amp;nbsp;go on Microsoft Update.&amp;nbsp; Because all Windows Update content is on Microsoft Update as well (but not vice-versa), one could look at that the other way around and say that all updates (Visual Studio and the .NET Framework)&amp;nbsp;go to Microsoft Update while only .NET Framework updates go to Windows Update.&amp;nbsp; All updates that go to either Windows Update or Microsoft Update must go to the Microsoft Download Center as well.&lt;/P&gt;
&lt;P&gt;Tables have been known to help:&lt;/P&gt;
&lt;P&gt;
&lt;TABLE class=MiscTable&gt;
&lt;CAPTION&gt;Developer Division Deployment Channels&lt;/CAPTION&gt;
&lt;THEAD&gt;
&lt;TR&gt;
&lt;TH&gt;Product&lt;/TH&gt;
&lt;TH&gt;Windows Update&lt;/TH&gt;
&lt;TH&gt;Microsoft Update&lt;/TH&gt;
&lt;TH&gt;Download Center&lt;/TH&gt;&lt;/TR&gt;&lt;/THEAD&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;.NET Framework&lt;/TD&gt;
&lt;TD&gt;Yes&lt;/TD&gt;
&lt;TD&gt;Yes&lt;/TD&gt;
&lt;TD&gt;Yes&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;Visual Studio 2005&lt;/TD&gt;
&lt;TD&gt;No&lt;/TD&gt;
&lt;TD&gt;Yes&lt;/TD&gt;
&lt;TD&gt;Yes&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;Visual Studio 2002, 2003&lt;/TD&gt;
&lt;TD&gt;No&lt;/TD&gt;
&lt;TD&gt;TBD&lt;/TD&gt;
&lt;TD&gt;Yes&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/P&gt;
&lt;P&gt;You may be saying to yourself, "I've never seen any Visual Studio updates on Microsoft Update."&amp;nbsp; That's true, but we're working on it.&amp;nbsp; Expect&amp;nbsp;to see updates targeting Visual Studio 2005 on Microsoft Update starting&amp;nbsp;in Q1 of calendar year 2006.&amp;nbsp; We will also be evaluating whether to service Visual Studio.NET 2002 and Visual Studio.NET 2003 in the same way.&amp;nbsp; These latter Visual Studio versions (2002, 2003) are more complicated because they were released before Microsoft Update existed and therefore were not built with Microsoft Update integration in mind.&amp;nbsp; We'll need to make do with what we have for these.&amp;nbsp; Let me know how we do!&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=415303" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/blairn/archive/tags/Work+in+Progress/default.aspx">Work in Progress</category><category domain="http://blogs.technet.com/blairn/archive/tags/Dimensions+of+Deployment/default.aspx">Dimensions of Deployment</category></item></channel></rss>