Last post Jun 20, 2009 12:25 PM by jthanassis
Mar 29, 2009 05:50 PM|smithym|LINK
can anyone give a helping hand, I been watching the videos for the mvc storefront and have create my own website using these techniques i.e. DDD, Repository pattern but i wish to use Entity Framework.
In the Interfaces it returns IQueryable but with the entity framework i should return ObjectQuery instead? - I will be using LINQ.
Also in the storedfront example it goes something like this IQueryable<Category> GetCategories();
As in the mvc stored the Category class was a build entity class (standard class) but with the entity framework these classes are prebuilt in the object context - are they not?
So i should need to build them.
I am a little confused, if anyone has any helpful example or code it would be really helpful.
As i say i have watched the videos from THe mvc storefront using linq2sql but really would like to use the entity framework.
entity framwork mvc repository pattern
Jun 20, 2009 12:25 PM|jthanassis|LINK
Do you really want to switch to Entity Framework?
I believe that using an ORM in software development is a good choice.
Microsoft has done a great job in c# and lately in ASP.NET MVC but for an ORM solution is a couple of steps behind.
I really don't know whether Microsoft will one day offer a good ORM for .Net or not.
Maybe in 2 years from now the impementation of Entity framework in .Net will be mature,stable and mainly light but not even Microsoft knows that right now.
They decided to focus on L2E and the Entity Framework and leave behind L2S and Linq-to-SQL Classes (that's a good choice but shows that even big companies make bad decisions from time to time).
Before switching to Entity Framework I would suggest to take a look at the following links:
Finally, here are some usefull links to start with the Entity Framework:
(stackoverflow is always a great place to find usefull information)
Currently I'm developing a clone of an existing CMS (written in classic ASP) using c#,ASP.NET MVC and L2S.
In the near future i will keep using c# and ASP.NET MVC but I will focus on NHibernate unless Microsoft has something interesting to show me. Right now there is no such thing. I really like Linq and I expect that Linq-to-NHibernate support will be much more
mature in the near future.
The only reason I replied to your initial question is to remind you that you should never follow a technology before looking around for a beter alternative and right now I strongly believe that the Entity Framework implementation for .NET is not the best solution
if we really need to use an ORM in our software.