What's New in the SP1 Beta?

Service Pack 1 de Microsoft Visual Studio 2008 y Microsoft .NET Framework 3.5... en versión BETA

Jorge Serrano - MVP Visual Developer - Visual Basic — Tue, 13 May 2008 10:05:05 GMT

Todos sabreis a estas alturas que el Service Pack 1 de Microsoft Visual Studio 2008 ha aparecido en versión

VS 2008 / .NET Fx 3.5 SP1 BetaでのDBまわり改善点

OPC Diary — Tue, 13 May 2008 13:00:28 GMT

ADO.NET team blog : What's New in the SP...

VS 2008 Sp1 Beta Links

Mike Taulty's Blog — Tue, 13 May 2008 13:54:55 GMT

Just links.... ScottGu Soma Entity Framework Data Services Download

SP1 Beta & EntityFramework

Сергей Лутай — Tue, 13 May 2008 16:29:01 GMT

В блоге ADO.NET команды есть подробная информация о перечне изменений, которые затронул SP1 Beta в EntityFramework

New EntityDataSource Control for ASP.NET

Diego's Blog — Tue, 13 May 2008 17:09:11 GMT

As it was announced today , the EntityDataSource is now part of Entity Framework, and a first beta version

Visual Studio 2008 SP1 Beta

Data Tools and Software Testing — Tue, 13 May 2008 19:03:45 GMT

It's great to see a lot of the work that has been going on in our product unit finally get into the hands

re: What's New in the SP1 Beta?

Darek — Tue, 13 May 2008 19:28:05 GMT

It's good to see all of these changes in SP1.

One more thing I could suggest is:

- add some functionality of designer from SQL Server. I mean about create of small subsets of diagrams which work on base model diagram. It could be like diagram view. Working with one big model diagram with about 50 - 100 or more entities is hard.

Maybe some kind of grouping entities in diagram could also help - with collapse/expand function.

Apart all of this - thanks for Your work.

re: What's New in the SP1 Beta?

int19h — Tue, 13 May 2008 20:39:00 GMT

"Update Model from Database" is nice, but what about the other way around? When I don't have to deal with legacy DBs, I'd much prefer to generate the (presumably optimal) database schema from my entity model, not the other way around - and have the former automatically updated when I edit the latter.

re: What's New in the SP1 Beta?

jamal@mavadat.net — Tue, 13 May 2008 20:50:17 GMT

Congratulations, well done!

Jamal Mavadat

VS 2008 SP1 Beta and .Net 3.5 SP1 Beta, what's new for EF?

Matthieu MEZIL — Tue, 13 May 2008 23:45:17 GMT

La Beta de VS 2008 SP1 Beta apporte beaucoup de nouveautés ( cf post de Scott Guthrie ) mais quand est-il

re: What's New in the SP1 Beta?

shawn — Wed, 14 May 2008 10:42:37 GMT

Any chance of introducing an option for transparent lazy loading of relationships before RTM? A configuration option baked into framework that did something like this would be absolutely fantastic:

http://blogs.msdn.com/jkowalski/archive/2008/05/12/transparent-lazy-loading-for-entity-framework-part-2.aspx

Having it as an option would make some scenarios a lot easier, especially for users migrating from LINQ to SQL or other O/RMs that support the transparent loading of relationships.

A little more about SP1 Beta and the EF

system.data.objects dev guy — Wed, 14 May 2008 11:55:26 GMT

Just a quick note to point out a few interesting things about the updated version of the EF which shipped

re: What's New in the SP1 Beta?

Adam Cooper — Wed, 14 May 2008 16:06:01 GMT

I don't want to discourage any of you from the tremendous work you're doing--there's no doubt that the Entity Framework will be groundbreaking--however, if the ADO.NET EF does not support some fundamental requirements for Domain Driven Design, I'm afraid I'm going to have to continue using an alternative solution such as NHibernate.

The EF will no doubt shine in the following respects:

- Powerful and strongly-typed query support via LINQ

- Sophisticated mapping of objects to tables

- Support for multiple databases

This by itself is a mouthful and you all deserve a lot of credit for your hard work in this space. I'm sure few of us appreciate how difficult your work has been. Nevertheless, there are several other key ingredients that must be in place before I (and others) will be able to move to the ADO.NET EF:

- Object-first development. The pattern I keep noticing with both LINQ to SQL and LINQ to Entities is one where we begin with the database and then use it to generate objects. But because it is the objects that are truly the heart of our software (and not the database, which is merely the cold persistence of our objects), I (and many others) find it much more useful to turn it the other way around, beginning with our objects, specifying a mapping, and then generating the database. I don't disagree that database-first development is an important scenario to have in the EF package, but without support for objects-first development I simply won't be moving to the EF.

- Pure POCO development in the domain layer. Along the same lines as the previous point, if the EF significantly restricts what I can or cannot do in designing my domain objects (such as requiring that I inherit from base classes or implement interfaces, etc.), I will continue using an ORM tool that doesn't hinder my ability to model the business domain.

- Automatic change-tracking without the need to be connected to the database while domain objects are being modified. For n-tier and web scenarios it is extremely important that we be able to work with our objects without having to be connected to the database and without the need for complicated re-attachment code. The community outcry over LINQ to SQL’s shortcomings in this area is enough to ensure that the ADO.NET EF will receive a similar loathing if it is not substantially better. We need the EF to allow us to connect-load-disconnect, change our objects, and then connect-save-disconnect, all without any pain.

Please forgive me if I have misrepresented what the EF does and does not support. If you have already addressed any of these points or if you are planning to before RTM, my sincere apologies. But from all I've read I'm left with the impression that the object-first, POCO, disconnected-development model will not be supported in EF version 1.0. If that's not true I'm sure there are other people like myself who would appreciate some clarification. In any case, perhaps you can clarify which of these points the EF supports, which it doesn't, and what your future plans are.

You guys are doing great stuff; we just want to use it! Once the ADO.NET EF supports the development model I've outlined above I think you'll see a swell of support. I can understand if you can't do it by version 1.0, but we'd sure like to know how much thought you're giving to Domain Driven Design and what your commitments are to this development philosophy.

Thanks much,

Adam Cooper

re: What's New in the SP1 Beta?

elisaj — Wed, 14 May 2008 20:20:39 GMT

Hi int19h,

Thank you for you comments. This is a scenario that we have heard many times and have worked very hard on. We had hoped to fit it into V1 (as mentioned in some of the comments threads on the blog previously). Unfortunately, when it came down to it, we wanted to get the product shipped and it just didn't fit. That said, it is at the top of our list for V2. You many also want to keep an eye on our Code Gallery site at http://code.msdn.microsoft.com/adonetefx. As the team continues working on this we are hoping to post some of our prototypes/samples here.

-Elisa Flasko, PM Data Programmability - MSFT

re: What's New in the SP1 Beta?

elisaj — Wed, 14 May 2008 20:47:42 GMT

Hi Adam,

Thank you for your feedback. We have definately received this message from many of our customers who are using Domain Driven Development techniques, and although it did not fit into V1 of the Entity Framework, it is a large part of our planning for V2. At this point, we are still in the planning stages and cannot say for sure what we will tackle in V2, but we are working with these customers to ensure that we tackle this scenario in the best way possible.

Thank you,

Elisa Flasko - PM Data Programmability

VS 2008 SP1 Beta and .Net 3.5 SP1 Beta, what's new for EF? 2

Matthieu MEZIL — Thu, 15 May 2008 01:33:02 GMT

En plus de ce post j'ai référencé avant-hier celui-ci

VS 2008 and .NET 3.5 SP1 Beta changes for LINQ to SQL, and more

LINQ in Action - LINQ Book & News — Thu, 15 May 2008 02:44:35 GMT

The ADO.NET team details on its blog what has changed for LINQ to SQL with the release of Visual Studio

VS 2008 and .NET 3.5 SP1 Beta changes for LINQ to SQL, and more

Fabrice's weblog — Thu, 15 May 2008 02:44:38 GMT

The ADO.NET team details on its blog what has changed for LINQ to SQL with the release of Visual Studio

VS 2008 and .NET 3.5 SP1 Beta changes for LINQ to SQL, and more

Fabrice's weblog — Thu, 15 May 2008 02:46:36 GMT

The ADO.NET team details on its blog what has changed for LINQ to SQL with the release of Visual Studio

more information ...about VS2008 SP1 and .NET FX 3.5 SP1

ccBoy's WebLog — Thu, 15 May 2008 13:41:37 GMT

ScottGu's - Visual Studio 2008 and .NET Framework 3.5 Service Pack 1 Beta http://weblogs.asp.net/scottgu/archive/2008/05/12/visual-studio-2008-and-net-framework-3-5-service-pack-1-beta.aspx

re: What's New in the SP1 Beta?

abishek.srikaanth — Thu, 15 May 2008 17:47:45 GMT

I have installed the SP1 Beta, but i dont see the Entity Framework Model in the Add new Item. Could you help please

re: What's New in the SP1 Beta?

R Raghu — Thu, 15 May 2008 18:58:57 GMT

Please take a look at forum thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3347714&SiteID=1

So far we have not received any resolution on the setup issue for the EF.

Thanks.

re: What's New in the SP1 Beta?

abishek.srikaanth — Fri, 16 May 2008 09:07:20 GMT

Link doesnt seem to help in solving the problem

VS2008 SP1 brings a new build of ADO.NET Entity Framework and LINQ to Entities

Paolo Pialorsi — Sun, 18 May 2008 17:57:57 GMT

In the last days has been released the beta version of Visual Studio 2008 Service Pack 1, including a

re: What's New in the SP1 Beta?

Arye Friedman — Mon, 19 May 2008 11:52:23 GMT

Hi,

Definitely great progress done. I am wondering if there is a way to port existing T-SQL-stored-procedures' based business logic to EF or DLINQ.

Thank you,

Arye Friedman

Visual Studio 2008 Service Pack 1 BETA is here with new Entity Framework and ADO.NET Data Services!

Hot Topics — Mon, 19 May 2008 22:12:30 GMT

Lots to read and download From the Data Programmability Team   SP1 Beta Download, what's new

ADO.NET team blog : What's New in the SP1 Beta?

Dating — Sun, 01 Jun 2008 12:56:12 GMT

This morning we announced the availability of the Visual Studio 2008 and .NET Framework SP1 Beta releases, and now you're probably wondering... well what's changed? Here goes... Across the Entity Framework we have made numerous bug fixes (more than 20

ADO.NET team blog : What's New in the SP1 Beta?

Weddings — Thu, 05 Jun 2008 19:59:31 GMT

re: What's New in the SP1 Beta?

Günter Zöchbauer — Thu, 24 Jul 2008 23:53:50 GMT

after inserting a ComplexType declaration using the xml editor the model can't be edited using the designer anymore (refuses to open and offers redirect to the xml editor)

In previous versions (beta 2/3) the mapping for ComplexType could easily edited in the designer after declaring the ComplexType in the xml editor

re: What's New in the SP1 Beta?

jemiller — Sat, 02 Aug 2008 06:43:40 GMT

I whole heartedly agree with everything that Adam Cooper said. I am in the exact same boat as him. As a user of Hibernate/NHibernate, I've always designed things the other way around. Being able to generate classes from an existing database is very useful, but, if you are designing a new app, it is less useful. The ability to get it to work as painlessly as possible with web services is also important.

re: What's New in the SP1 Beta?

Адриан — Sun, 12 Apr 2009 02:40:03 GMT

Занимательная и интересная статья у вас. В отличие от большинства остальных подобных минимум воды! :)

re: What's New in the SP1 Beta?

Егор Макаров — Fri, 24 Apr 2009 14:17:08 GMT

IMHO, эта тема слишком сложная для новичка :)