<?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>.NET Framework SP's Available!</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx</link><description>For those who haven't gotten their hands on an Windows XPSP2 CD, new .NET Framework SP's are now available, for versions 1.0 and 1.1 (the first version of 2.0, or "Whidbey" is still yet to be released). Here are the links to Microsoft's download center,</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: .NET Framework SP's Available!</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx#223002</link><pubDate>Tue, 31 Aug 2004 00:05:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:223002</guid><dc:creator>Brian Hampson</dc:creator><description>Thanks for the links!</description></item><item><title>Theo Yuang Points out that MS has released SP1 for .Net Framework 1.1</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx#223005</link><pubDate>Tue, 31 Aug 2004 03:07:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:223005</guid><dc:creator>Brian Hampson - My Life and Things I Find Interest</dc:creator><description /></item><item><title>.net Framework Service Packs available</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx#223039</link><pubDate>Tue, 31 Aug 2004 03:45:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:223039</guid><dc:creator>An attempt at structured thought.</dc:creator><description>.net Framework Service Packs available</description></item><item><title>re: .NET Framework SP's Available!</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx#224492</link><pubDate>Thu, 02 Sep 2004 04:54:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:224492</guid><dc:creator>Brian Hampson</dc:creator><description>Quick Q:&lt;br&gt;&lt;br&gt;If I build to the SP1 for 1.1 will target systems also require it to be installed?&lt;br&gt;&lt;br&gt;Most notably, I'm referring to: &lt;br&gt;&lt;br&gt;System.Drawing.Image.FromStream(Stream stream, bool useICM, bool validateImageData)&lt;br&gt;&lt;br&gt;If I use the new params will I get bitten if target platform isn't using SP1?&lt;br&gt;&lt;br&gt;</description></item><item><title>re: .NET Framework SP's Available!</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx#225041</link><pubDate>Fri, 03 Sep 2004 02:25:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:225041</guid><dc:creator>piers</dc:creator><description>Where's the MSDN documentation on this? I can't believe microsoft's going to release an update to the .NET framework without actually telling anybody about how to test to make sure their applications don't die on everyone's machines when they update.&lt;br&gt;&lt;br&gt;what are we supposed to do, scramble to test the day it appear on windows update?&lt;br&gt;&lt;br&gt;ridiculous.</description></item><item><title>re: .NET Framework SP's Available!</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx#225310</link><pubDate>Fri, 03 Sep 2004 16:28:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:225310</guid><dc:creator>Theo Yaung</dc:creator><description>To answer Brian's question:&lt;br&gt;&lt;br&gt;Just as people have to bootstrap the framework installer to ensure that their endusers have the .NET Framework, you'd have to bootstrap the SP installer too.&lt;br&gt;&lt;br&gt;You can use reflection to see if that particular method overload is available, and then call it reflectively (akin to VB's late binding).  That's the only way I can think of at the moment.  Since the framework SP's are on WU as a critical update, after a while, it will be somewhat more likely that your enduser will have the SP1 version of the framework, rather than the original RTM (Release To Market) version.&lt;br&gt;&lt;br&gt;In regards to Piers' comment:&lt;br&gt;You should read the KB articles to find out what changes to test against.  In addition, there was a &amp;quot;Tech Preview&amp;quot; program, where a beta of the framework SP's was made available to test against, since July 1st.&lt;br&gt;&lt;br&gt;We've also posted about the framework updates  and Tech Preview on MSDN.  The obsoleted Tech Preview page is here:&lt;br&gt;&lt;br&gt;&lt;a target="_new" href="http://msdn.microsoft.com/netframework/downloads/updates/sptechpreview/"&gt;http://msdn.microsoft.com/netframework/downloads/updates/sptechpreview/&lt;/a&gt;&lt;br&gt;&lt;br&gt;It appeared as a headliner in July, when it came out.  Though I will let the content team know that they should emphasize the upcoming SP's more on their webpage.&lt;br&gt;&lt;br&gt;I'll also try to loop in a tester from our team to give some tips on how to test for application compatibility.</description></item><item><title>re: .NET Framework SP's Available!</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx#226112</link><pubDate>Mon, 06 Sep 2004 19:01:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:226112</guid><dc:creator>Brian Hampson</dc:creator><description>Yes, I see them now as critical updates on Windows Update.  The thing is that they won't auto install.  They just sit there, waiting.  I've got a PC sitting there, and it has been happily auto installing updates all along, but these just sit there, and won't install :(</description></item><item><title>re: .NET Framework SP's Available!</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx#226164</link><pubDate>Mon, 06 Sep 2004 22:24:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:226164</guid><dc:creator>Theo Yaung</dc:creator><description>Hmm... I don't know of any reason why they'd do that at the moment.  I didn't configure the delivery of our patches via Windows Update / AutoUpdates (a.k.a. System Update Service).&lt;br&gt;&lt;br&gt;I'm talking with a co-worker about this issue, and will try to post back to this comment line ASAP.&lt;br&gt;&lt;br&gt;Are you running managed apps in the background? Which version(s) of the framework are you patching? Here're some questions that would be helpful:&lt;br&gt;&lt;br&gt;(1) Operating System (1 of the following)&lt;br&gt;    a. Windows Server 2003 (this affects .NET 1.1)&lt;br&gt;    b. Windows XP for Tablet PC or Windows Media Center&lt;br&gt;    c. Other versions of XP, 2000, or NT&lt;br&gt;    d. Windows 95, 98, or Millenium&lt;br&gt;&lt;br&gt;(2) Framework Versions installed (any of the following)&lt;br&gt;    a. 1.0 framework&lt;br&gt;    b. 1.1 framework&lt;br&gt;    c. 2.0 framework beta(s)&lt;br&gt;&lt;br&gt;(3) Do you run managed applications in the backround? (these can also be Windows services, or Office add-ins, etc.).&lt;br&gt;&lt;br&gt;Those are some questions that I can think of, off the top of my head.  In the meanwhile, I'll try to see what our representative to Windows Update says about our framework deliver over AutoUpdates.&lt;br&gt;&lt;br&gt;Thanks!</description></item><item><title>re: .NET Framework SP's Available!</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx#226484</link><pubDate>Tue, 07 Sep 2004 21:25:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:226484</guid><dc:creator>Brian Hampson</dc:creator><description>Thanks for looking into it. &lt;br&gt;&lt;br&gt;My machine at home is Win2KSP3,  I'm not running any background managed code that I can think of.&lt;br&gt;&lt;br&gt;I notice that over the weekend, our SUS server at work has picked up the SP's.  I'll see if they go to the client PC's now that I've approved them.  (&amp;lt;frown&amp;gt;Sure would be nice if SUS somehow notified an email address when new updates arrived &amp;lt;/frown&amp;gt;).&lt;br&gt;&lt;br&gt;I'll keep you informed.</description></item><item><title>re: .NET Framework SP's Available!</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx#227431</link><pubDate>Thu, 09 Sep 2004 16:24:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:227431</guid><dc:creator>Brian Hampson</dc:creator><description>OK....they're rolling in now as critical updates...I don't know why they didn't before.  I could see them sitting there as critical, but they wouldn't go in.  Odd.  Thanks Theo!</description></item><item><title>Theo Yuang Points out that MS has released SP1 for .Net Framework 1.1 &amp;laquo; Brian Hampson - Life and Other Things</title><link>http://blogs.msdn.com/theoy/archive/2004/08/30/222998.aspx#6984114</link><pubDate>Sat, 05 Jan 2008 01:54:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6984114</guid><dc:creator>Theo Yuang Points out that MS has released SP1 for .Net Framework 1.1 « Brian Hampson - Life and Other Things</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://dragonspeed.wordpress.com/2004/08/30/theo-yuang-points-out-that-ms-has-released-sp1-for-net-framework-11/"&gt;http://dragonspeed.wordpress.com/2004/08/30/theo-yuang-points-out-that-ms-has-released-sp1-for-net-framework-11/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>