Working With Large Models In Entity Framework – Part 1

re: Working With Large Models In Entity Framework – Part 1

Eryaman hali yikama — Thu, 10 Jun 2010 15:22:43 GMT

Good information and good way your blog post. Good luck blogger man.

re: Working With Large Models In Entity Framework – Part 1

Tony — Tue, 22 Dec 2009 19:13:49 GMT

What's wrong with the same type defined in multiple models? For example, with AdventureWorks, tables in the Person schema are related both to tables in the Sales and Human Resources schemas. Why not simply create two models, one for Sales and another for Human Resource, but with Person tables in both models? What are the problems with this approach?

re: Working With Large Models In Entity Framework – Part 1

alex — Sun, 13 Dec 2009 06:52:12 GMT

could your rewrite the petshop demo whit Entity Framework, so we can get a best practice sample.

re: Working With Large Models In Entity Framework – Part 1

Luc — Fri, 09 Oct 2009 06:12:57 GMT

52 entities, 55 associations (Foreign keys)

The Validate step worked slower and slower.

Now it crashes both in VS and at run time ...

EF is big and clumsy. I even wonder if it can be fixed. Many unnecessary features

that should have been orthogonal to the framework not built in.

I actually wanted to use Linq to SQL, that's a lean piece of software. But MS drops it and picks EF as the "winner".

I apologize for being this harsh but it's ridiculous to consider a 50-100 tables system as being big. What's a 500 tables system then?

I concur with Juan above ...

re: Working With Large Models In Entity Framework – Part 1

juan — Sun, 09 Aug 2009 00:08:42 GMT

una porkeria su Entity Framework..

re: Working With Large Models In Entity Framework – Part 1

zerrin egeliler — Thu, 23 Jul 2009 19:41:39 GMT

I'm really looking forward to seeing these and have donloaded them but they are the raw files. One of the points you have made is that using these patterns you can do all of the work in the designer. Any chance of sharing some EDMX files so we don't have to dizzy ourselves looking at the raw xml and moving back and forth from one file to another to mentally put it all together?

re: Working With Large Models In Entity Framework – Part 1

ssk sorgulama — Thu, 23 Jul 2009 17:22:25 GMT

re: Working With Large Models In Entity Framework – Part 1

radyo dinle — Sun, 19 Jul 2009 17:31:24 GMT

Last week, a customer asked me how to solve a big EDM performance problem? In his case, his model was

re: Working With Large Models In Entity Framework – Part 1

Andreas — Wed, 24 Jun 2009 12:00:35 GMT

Does anyone know if there has been some improvement for big database structure? Does the VS 2010/.NET 4 handle it better?

We are in the development process of an application that will grow. For the moment and for the next year we are not expecting a very huge model, but it might become large later on.

What has changed with the new upcoming versions?

Thanks

How to split your EDM?

Matthieu MEZIL — Wed, 27 May 2009 16:28:11 GMT

One of my customers wants to code an ERP. To make it, he wants to use EF. His DB has more than 600 tables