<?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 3.5 makes first appearance in CTP</title><link>http://blogs.msdn.com/pandrew/archive/2007/03/01/net-framework-3-5-makes-first-appearance-in-ctp.aspx</link><description>This week we released the Visual Studio codename "Orcas" March 2007 CTP and this is the first time that features from .NET Framework 3.5 have been included. I've already seen this on Matt Winklers blog and Somasegars blog . I would recommend you get the</description><dc:language>en-NZ</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>.NET Framework 3.5 makes first appearance in CTP</title><link>http://blogs.msdn.com/pandrew/archive/2007/03/01/net-framework-3-5-makes-first-appearance-in-ctp.aspx#1781646</link><pubDate>Fri, 02 Mar 2007 00:35:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1781646</guid><dc:creator>WF Team Bloggers</dc:creator><description>&lt;p&gt;This week we released the Visual Studio codename &amp;quot;Orcas&amp;quot; March 2007 CTP and this is the first time that&lt;/p&gt;
</description></item><item><title>[AUTOSAVED] .Net Framework 3.5 CTP...</title><link>http://blogs.msdn.com/pandrew/archive/2007/03/01/net-framework-3-5-makes-first-appearance-in-ctp.aspx#1785016</link><pubDate>Fri, 02 Mar 2007 08:37:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1785016</guid><dc:creator>SQL Server 2005 and .NET Development Blog</dc:creator><description>&lt;p&gt;Schlag auf Schlag, geht es mit den .Net Framework Versionen derzeit, aber das war ja irgendwie abzusehen.Das .Net Framework 3.5 hat jetzt erstmals Eingang in die Orcas-CTP (Orcas=der in Entwicklung befindliche Nachfolger von Visual Studio 2005)&lt;/p&gt;
</description></item><item><title>Just got used to .NET 3.0?  Well 3.5 is nearly here...</title><link>http://blogs.msdn.com/pandrew/archive/2007/03/01/net-framework-3-5-makes-first-appearance-in-ctp.aspx#1785800</link><pubDate>Fri, 02 Mar 2007 11:11:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1785800</guid><dc:creator>Insane World</dc:creator><description>&lt;p&gt;Visual Studio codename &amp;amp;quot;Orcas&amp;amp;quot; March 2007 CTP has been released, and it contains aspects of&lt;/p&gt;
</description></item><item><title>re: .NET Framework 3.5 makes first appearance in CTP</title><link>http://blogs.msdn.com/pandrew/archive/2007/03/01/net-framework-3-5-makes-first-appearance-in-ctp.aspx#1789739</link><pubDate>Fri, 02 Mar 2007 23:07:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1789739</guid><dc:creator>Charles Chen</dc:creator><description>&lt;P&gt;Ugh!&lt;/P&gt;
&lt;P&gt;Why all this confusion?&lt;/P&gt;
&lt;P&gt;First it's .Net 3.0 (but it's not *really* a new version, we just added some libraries...)&lt;/P&gt;
&lt;P&gt;Now it's .Net 3.5 (this time, we actually changed the language specs, but we're going to release it as a point release)&lt;/P&gt;
&lt;P&gt;How does this make any sense at all? &amp;nbsp;Is C# going to be renumbered to C# 3.0? &amp;nbsp;3.5? &amp;nbsp;&lt;/P&gt;
&lt;P&gt;IMO, .Net 3.0 should have been called "Extensions for .NET 2.0" or ".NET 2.1" or ".NET 2.0 Plus!" or something less...misleading. &amp;nbsp;You can't begin to fathom how confusing it is to managers when you explain to them this asynchronous numbering scheme...&lt;/P&gt;</description></item><item><title>re: .NET Framework 3.5 makes first appearance in CTP</title><link>http://blogs.msdn.com/pandrew/archive/2007/03/01/net-framework-3-5-makes-first-appearance-in-ctp.aspx#1874495</link><pubDate>Tue, 13 Mar 2007 20:50:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1874495</guid><dc:creator>Iskander Sierra</dc:creator><description>&lt;p&gt;Please, stop calling your libraries .NET Framework x.0. Use minor version numbers (they've been invented for something) or use WPF.NET Framework 1.0, WCF.NET Framework 3.1415, or whatever, but differentiate them please, no more .NET Framework versions if CLR does not change.&lt;/p&gt;
&lt;p&gt;My heart blows each time I hear that, (joking).&lt;/p&gt;
&lt;p&gt;Congratulations to all the MS teams involved in making developer's lives easier and joyful, you are doing an excelent job, really.&lt;/p&gt;</description></item><item><title>re: .NET Framework 3.5 makes first appearance in CTP</title><link>http://blogs.msdn.com/pandrew/archive/2007/03/01/net-framework-3-5-makes-first-appearance-in-ctp.aspx#1888852</link><pubDate>Thu, 15 Mar 2007 21:08:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1888852</guid><dc:creator>Mike Greenway</dc:creator><description>&lt;p&gt;Great! Looking forward to the new tools.&lt;/p&gt;</description></item><item><title>re: .NET Framework 3.5 makes first appearance in CTP</title><link>http://blogs.msdn.com/pandrew/archive/2007/03/01/net-framework-3-5-makes-first-appearance-in-ctp.aspx#2123827</link><pubDate>Sat, 14 Apr 2007 04:55:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2123827</guid><dc:creator>Jonas</dc:creator><description>&lt;p&gt;I agree with Charles; if anything, the class library &amp;quot;3.0&amp;quot; should really have been 2.5 as it's implemented on the 2.0 compilers, and this &amp;quot;3.5&amp;quot; should have been 3.0. But that's been discussed quite a bit now, and will of course not change at this point with 3.0 already out. :-(&lt;/p&gt;</description></item><item><title>re: .NET Framework 3.5 makes first appearance in CTP</title><link>http://blogs.msdn.com/pandrew/archive/2007/03/01/net-framework-3-5-makes-first-appearance-in-ctp.aspx#2289957</link><pubDate>Thu, 26 Apr 2007 23:46:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2289957</guid><dc:creator>sandy</dc:creator><description>&lt;p&gt;Man, Its getting hard to catch up with newer .NET versions. We are still working with .NET 1.1 and everything works great. Don't know why we would need .NET 3.5 ???&lt;/p&gt;</description></item><item><title>Codename: Astoria and Jasper at Mix07</title><link>http://blogs.msdn.com/pandrew/archive/2007/03/01/net-framework-3-5-makes-first-appearance-in-ctp.aspx#2355308</link><pubDate>Tue, 01 May 2007 13:54:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2355308</guid><dc:creator>Simon Thorneycroft and Jonathan Hodgson</dc:creator><description>&lt;p&gt;Aside from the Silverlight announcements which seem to have stolen the show so far at Mix07. A couple...&lt;/p&gt;
</description></item><item><title>LINQ and interop with other (non-Microsoft) databases</title><link>http://blogs.msdn.com/pandrew/archive/2007/03/01/net-framework-3-5-makes-first-appearance-in-ctp.aspx#2819138</link><pubDate>Wed, 23 May 2007 19:59:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2819138</guid><dc:creator>All About Interop</dc:creator><description>&lt;p&gt;This topic came up on an internal mailing list at Microsoft. The question is, will LINQ be usable with&lt;/p&gt;
</description></item></channel></rss>