Feeds:
Posts
Comments

Posts Tagged ‘ef’

From the picture Julie painted it sounds like the Entity Framework is finally coming together. While I’m sure it’s far from perfect the latest version would seem to have addressed MANY of the issues I ran into the first time I used it. With EF being such a strong contender, it would seem my decision has come down to nHibernate and EF. Microsoft safety versus the guys that have been doing it right for a lot longer… tough call!

Julie Lerman on Entity Framework 4.0Julie is back to talk about the improvements to the Entity Framework in version 4.0.

via .NET Rocks!.

Advertisements

Read Full Post »

After inquiring on the official forums about new features in Entity Framework 4.0 around join tables this is what I heard back. In short, no new news. 😦 Which is too bad. Our model doesn’t really model entities until we have some way of hiding the join tables or otherwise demoting them to second-class status.

Your understanding is correct, and, no, there aren’t any substantial additional workarounds in EF4. One of the fundamental problems when you have additional properties on your join tables is that you still need some mechanism to access those properties. So if they were truly hidden, that would cause other difficulties. Our current thinking is that in some future release we’ll not hide them per se, but we will provide mechanisms to make it easier to have a collection or reference that represents a “double-hop” from one entity to the join-table-entity and then on to the entity or entities on the other side. You can simulate some of this yourself now by creating a property on your entity which is of type IEnumerable or something like that where the getter does the double hop, but of course that doesn’t help you when it comes time to do a linq query across both hops or that kind of thing.

– Danny

via Join Table Hiding Improvements in EF4? Workarounds?.

Read Full Post »

Just finished another excellent podcast from .NET Rocks which this time discussed the new features of the Entity Framework which is currently out in beta. While I haven’t had a chance to give it a try myself I’m very interested in what Daniel Simmons described. Having written off the EF as “not ready yet” and expecting the new release to still not meet my needs, I was very pleasantly surprised to hear that new features will make it into the final release that weren’t “supposed” to as of a few months back. I definitely need to reevaluate because based on what I heard in the interview the EF may be just a good a fit for me as nHibernate. I definitely recommend anyone interest in ORM check out the interview. (And go write some code)

Daniel Simmons is back this time to talk about the new features of ADO.NET Entity Framework version 4.

Daniel SimmonsDaniel Simmons is dev manager for the Entity Framework and LINQ to SQL team where his mission is to build a team and a product that will fundamentally change the way we build data-centric software. He has been at Microsoft for 10 years working on a variety of products. Before coming to Microsoft he worked as a consultant, founded an ISP and engaged in various other software pursuits.

.NET Rocks!.

Read Full Post »

One of my biggest complaints about the Express versions of Sql Server is that Sql Profiler is specifically excluded, a full Sql Server license is required instead. I managed to do without Sql Profiler just fine until I was working on some Entity Framework code and wanted the see the sql getting generated. It certainly made sense to verify the operation of the application during development (using Sql Express) rather than waiting until after deployment. Unfortunately Microsoft doesn’t see eye-to-eye with me on this issue. Most fortunately xSQL Software has stepped in to fill the void, allowing their profiler xSQL Profiler to be used on up to two server instances for free. I’ll definitely be testing this app the first chance I get!

xSQL Profiler

Monitor SQL Server events – multiple servers, one location, no agents

Trace multiple SQL Servers at once

Use predefined events or define custom events

Powerful filtering capability – precise tracing

Schedule traces to run when and where you want

Customize the frequency with which data is collected

Flexible reporting interface

Use for performance, auditing and compliance

SQL Server 2000, SQL Server 2005 and SQL Server 2008

Monitor SQL Server events – xSQL Profiler – xSQL Software.

Read Full Post »

Interesting if somewhat scathing discussion of using the Entity Framework for n-tier applications from the developers/designers of the next version of the Entity Framework. The feedback has inspired me to look at nHibernate again, and makes me wonder if the Entity Framework is really as safe a bet as one would assume Microsoft’s implementation of a technology would be.

The first version of Entity Framework provides convenient ways to load, manipulate and persist objects and relationships. As with many other O/RMs, Entity Framework has a state manager that tracks every change made. Existing objects are typically loaded first from the database, later modified, and finally the changes are saved back to the store.

Another feature, full graph serialization, makes it very easy for developers to ship around object graphs representing snapshots of the current state of the world, across execution boundaries.

The next version of Entity Framework will also support Persistence Ignorance. Therefore object graphs can now be made of POCO instances, which WCF now also supports.

Nonetheless, there is a task that belongs in any N-Tier application that still requires a great amount of work for developers using EF: decoding messages that represent state changes performed by the client, meant to be processed or persisted by the service.

via Entity Framework Design : N-Tier Improvements for Entity Framework.

Read Full Post »