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 Team Suite-Only VPC to review the new features in .NET Framework 3.5.
Brief on .NET Framework 3.5
Many ISV’s, enterprises and even our own Microsoft product teams are successfully building on the new features WF, WCF, WPF and CardSpace in the .NET Framework 3.0. Microsoft plans to continue to invest in the .NET Framework developer platform and in support of existing users the .NET Framework 3.5 has no serious breaking changes so existing applications built for .NET Framework 2.0 or .NET Framework 3.0 will continue to execute. The .NET Framework 3.5 adds new features in several major technology areas.
.NET Framework 3.5 will ship with Visual Studio codename ”Orcas” and will be available for separate download from MSDN.
Just The Server Side (WF and WCF)
Here's some detail of the new things to look for from WF and WCF.
Matt Winkler already has a good run down on several of these these blogged.
This week we released the Visual Studio codename "Orcas" March 2007 CTP and this is the first time that
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)
Visual Studio codename "Orcas" March 2007 CTP has been released, and it contains aspects of
Why all this confusion?
First it's .Net 3.0 (but it's not *really* a new version, we just added some libraries...)
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)
How does this make any sense at all? Is C# going to be renumbered to C# 3.0? 3.5?
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. You can't begin to fathom how confusing it is to managers when you explain to them this asynchronous numbering scheme...
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.
My heart blows each time I hear that, (joking).
Congratulations to all the MS teams involved in making developer's lives easier and joyful, you are doing an excelent job, really.
Great! Looking forward to the new tools.
I agree with Charles; if anything, the class library "3.0" should really have been 2.5 as it's implemented on the 2.0 compilers, and this "3.5" 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. :-(
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 ???
Aside from the Silverlight announcements which seem to have stolen the show so far at Mix07. A couple...
This topic came up on an internal mailing list at Microsoft. The question is, will LINQ be usable with