Why doesn’t Entity Framework support ODBC?

The Entity Framework doesn’t require new data providers, exactly. Rather, it requires Entity Framework providers which extend existing data providers, to provide additional services required by the Entity Framework, such as complex SQL generation, which are not part of the existing ADO.NET data model. I don’t think that there’s anything stopping anyone from writing an … Read more

ADO.Net Entity Framework An entity object cannot be referenced by multiple instances of IEntityChangeTracker

[Update] Because L2E is used you need to save all the linked objects first before you can save the main object. Which makes sense otherwise you would create (in my example) an artist without it’s contact object. This isn’t allowed by the database design. [/Update] Here’s my implementation which worked. [AcceptVerbs(HttpVerbs.Post)] public ActionResult Create([Bind(Exclude = … Read more

How to in-code supply the password to a connection string in an ADO.Net Entity Data Model

When you create your context, you can set a connection string. To build this connection string, you can parse the connection string without the password with an EntityConnectionStringBuilder and then parse the inner connection string with an other ConnectionStringBuilder, depending on your browser. Then you can set the password and pass it to the constructor. … Read more

Do you think it’s advantageous to switch to Entity Framework? [closed]

IMO, not at the moment. It is clear (from recent announcements especially) that EF is in for some heavy revisions as the “thunderdome” scenario plays out between LINQ-to-SQL and EF. Whatever happens, EF (in a few years) will almost certainly look quite different to EF today. Or certainly “different enough” ;-p As such, my view … Read more