UPDATE: Added note about removing previous versions before installing this CTP.
The ADO.NET Entity Framework June 2007 CTP is now available. This CTP contains updates to the ADO.NET Entity Framework since the Visual Studio Codename "Orcas" Beta 1 release, including changes in Object Services, Query, Entity Client, and the Entity Data Model Wizard in Visual Studio. Some of the new features include IPOCO, detaching from long-running ObjectContext instances, multiple entity sets per type, support for referential integrity constraints, span support, transactions, serialization, no more default constructors in code-generated classes, improvements to stored procedure support, access to the underlying store connection, directory macros in the entity connection string to support hosted scenarios, native SQL read-only views, UNICODE support in Entity SQL, query plan caching, and canonical functions in Entity SQL. We will have future posts that go into more detail about these new features.
Be sure to read the installation instructions carefully on the download page--this is a CTP after all. One key thing to highlight is the .NET Framework v3.0 requirement. Although the Visual Web Developer Codename "Orcas" Express Edition June 2007 CTP is supposed to install this version of the .NET Framework if it isn't already present, the installation fails if the .NET Framework v3.0 is missing. If you're running Vista, it's already on your machine. Otherwise, you can download it from the Microsoft.com Download Center.
Installation instructionsThe ADO.NET Entity Framework June 2007 CTP should be installed only on non-production computers.
SamplesOur samples are on CodePlex. We will be adding more samples in the next couple of weeks that demonstrate the new features in this release.
Visual Web Developer Express Edition onlyThis is a CTP and the only edition of Visual Studio that works for this release is Visual Web Developer Express. This means that you will only be able to author Web sites in Visual Studio. Nothing prevents you from building console applications or WinForms applications outside of Visual Studio and building them with MSBuild and a .NET Framework compiler, but you will not be able to work on those project types inside Visual Web Developer Express.
The ADO.NET team has released the latest bits for the ADO.NET Entity Framework with the June 2007 CTP
Overview This CTP contains updates to the ADO.NET Entity Framework since the Visual Studio Codename "Orcas"
ADO.NET Entity Framework June 2007 CTP now available ADO.NET Entity Frameworkの新しいCTPがでたそうです。なぜかこのＣＴＰはVWDのCTP上にしかインストールできないそうで。。。なんでだろう...
Hey folks, It has been longer in arriving than I would have liked, but the June CTP of the Entity Framework
Back in April, the ADO.Net Team has announced that the ADO.Net Entity Framework will not ship with Visual
There are a fair number of new and improved features in this release - check the list out at http://blogs.msdn.com/adonet/archive/2007/07/02/ado-net-entity-framework-june-2007-ctp-now-available.aspx
I understand that the iPhone gets a lot of hype, but was it really necessary to introduce iPOCO? ;)
Seriously, What does the 'I' stand for?
The "i" in IPOCO stands for "interface" and follows the .NET Framework naming conventions that all interfaces should have names that start with "i". Danny Simmons explains more on his blog post at http://blogs.msdn.com/dsimmons/archive/2007/07/03/june-ctp-of-the-entity-framework-is-finally-out.aspx
The June CTP of Entity Framework was released earlier this week. It includes work from the milestone
The Visual Web Developer Express Edition only limitation in the Entity Framework June CTP means that
Cool stuff! Just installed it, and it looks promising.
The latest version of the ADO.NET Entity Framwork Community Technology Preview has been released. You
For those of you who have been living under a rock, here is the ADO.NET team announcement of fresh bits