The .NET 3.0 July CTP can be downloaded from here:http://www.microsoft.com/downloads/details.aspx?FamilyId=62057A6F-185F-41DB-ABE5-678F6FC388F0&displaylang=en
Does this include ADO.NET 3.0?
If not, when ADO.NET 3.0 is released, will it be part of a .NET 3.0 CTP? ...or a standalone CTP?
Michael.
The July CTP does not include the ADO.NET Entity Framework. The team is currently working on a stand alone CTP for the ADO.NET Entity Framework to be released later this summer (target of August).
What is the forecast looking like for an ADO.NET CTP in August?
A) bright?
B) partially cloudy?
C) thick fog - visibility zero?
Cheers,
Michael.
Since the LINQ forum has announced that there won't be any more LINQ CTP's, what is the prognosis of a LINQ to Entity CTP? Are we really going to have to wait for Orcas Beta 1?
Jim Wooley
http://devauthority.com/blogs/jwooley
Thanks Daniel,
Maybe we can get SteveB and Ozzie to adopt this new forecasting terminology? :-)
Thanks again,
Michael.
The forcasting model is about as accurate as anything else we have from MSFT at the moment. ;-). Murphy's law would indicate that it will come out 2 days before my next major talk (at the Jacksonville FL Code Camp on 8/26). I'm not privy to any inside information so I have no way of knowing if or when a release is coming so please don't rely on that date for anything other than a bit of self-deprecating humor.
Jim Wooley
http://devauthority.com/blogs/jwooley
It's available today - checkout http://www.microsoft.com/downloads/details.aspx?FamilyId=B68F6F53-EC87-4122-B1C8-EE24A043BF72&displaylang=en
Michael.
ADO.NET vNext will not be included in .NET 3.0. (that's why we're just calling it "vNext" for now).
Pablo Castro
ADO.NET Technical Lead
Microsoft Corporation
I think the only reason anyone would have ever thought that ADO.NET vNext was going to be a part of .NET 3.0, was because people assumed C# 3.0 (which is going to be C# vNext now?), and .NET vNext (Which was thought to be .NET 3.0) were all pushed out of their home by WinFX which took the .NET 3.0 name.
Pablo - I can't imagine you guys at Microsoft are too happy with this confusion caused either. I know we guys out here in the field are quite annoyed that .NET 3.0/WinFX naming has caused so much confusion. Seriously, did they even consult the product teams before this renaming?
Sahil Malik
http://blah.winsmarts.com
PS: Sorry but this was too blogworthy - http://blah.winsmarts.com//2006-9-Next_NET_framework_version_number.aspx
I think that WinFX shouldn't been called .NET 3.0. Maybe developers can assume that .Net 3.0 isn't a new Framework, no new languages, etc... But comercially this change of name will confuse a lot.
If someone is agree with me you can sign for "Reverse WinFX Petition"
Jesus Jimenez
http://blogs.clearscreen.com/dtax
Jesus Jimenez -
I feel renaming .NET 3.0 back to WinFX or something else this late in the cycle will cause EVEN MORE confusion. It was a mistake to name it .NET 3.0 - no qualms about that, but let us just count our losses and move on for now, and hope that MSFT will consider asking their product teams before making silly name changes going forward.
Sahil Malik
http://blah.winsmarts.com
I'll take the heat on behalf of the company on this one :)
Let me try to shed some light on versioning story, focused on how it impacts ADO.NET:
The current version of the .NET Framework is 2.0.
The next version that will ship when Windows Vista ships is .NET Framework 3.0. As per Soma's blog it will ship with Windows Vista and will also be available for Windows XP and Windows Server 2003. The 3.0 release contains the 2.0 bits plus the following:
- Windows Presentation Foundation
- Windows Communication Foundation
- Windows Workflow
- Windows CardSpace
We don't expect to make any significant updates to ADO.NET in .NET 3.0. The Entity Framework in ADO.NET is not targeting (never has) the 3.0 release of .NET.
What you're seeing right now around the ADO.NET Entity Framework is work that we plan to ship in the version after .NET 3.0 which is code named "Orcas". We haven't locked on a final version number for Orcas yet. BradA talks about the possibility of it being 3.5 in his blog post at http://blogs.msdn.com/brada/archive/2006/06/11/627128.aspx.
I would like to hightlight this though: these are our current plans, but it's early in the project cycle so things can definitely change. Just take this as current thinking, not as something we're committing to.
I hope this helps. If there are any more details I can provide on this please let me know.
Pablo Castro
ADO.NET Technical Lead
Microsoft Corporation
