[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 602
  • Last Modified:

Entity Framework with VS 2010 - ASP.net

I am looking at putting together the pro's and cons between utilizing the Entity Framework - LINQ - or just writing ADO.net the way common to previous versions of Visual Studio prior to VS 2008.  It seems that LINQ is not a viable solution as my understanding is it is going away or not supported.


I would really like to gain two things from this question in order to provide points.

1:  Web Samples
2)  Pro's and Cons - Success Stories.


Please keep in mind that am just putting together a demo for now - a mock website that just demonstrates the capabilities.

I build websites with the concept of a FrontEnd - BAL - DAL and SQL 2005 on the backend for now.

Once I have a working sample in this type of architecture - I will assign points and close the question.


Thanks!
0
Robb Hill
Asked:
Robb Hill
  • 4
  • 2
2 Solutions
 
Bob LearnedCommented:
1) LINQ-to-XSD will be going away, but I still use it for small utility applications, as it is easier to implement than Entity Framework.

2) LINQ will not be going away for quite a while, because it is totally awesome!!

3) I had nothing but problems with the Entity Framework 4 that came with 2010, but with Entity Framework 4.1 (additional install), I believe that it is now becoming a viable solution, since it now supports the code-first approach for data modeling.

4) I am a bigger fan of NHibernate 3 with fluent interface

5) I am not exactly sure what kind of samples that you are looking for, so it would be difficult to pick out just the right needle in the proverbial haystack.
0
 
Robb HillSenior .Net DeveloperAuthor Commented:
I found this link that using the Contoso University as a sample.  This utilizes the data-first model.

Why do you prefer the code first approach....I would think the choice of doing one or the other would be based on the application rather which is better.  
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Robb HillSenior .Net DeveloperAuthor Commented:
Is your main issue with Entity due to complexity?  If so maybe you could elaborate....Im finding that just wiring it up to a database and putting a basic frontend that it takes just minutes ....but I havent done much except for examples so not sure where the headache would be.
0
 
Bob LearnedCommented:
My main issues with Entity Framework were the exceptions, the model validation errors, the bizarre behavior when working with foreign keys.  

Let's peer into the mind of Scott Guthrie:

Code-First Development with Entity Framework 4
http://weblogs.asp.net/scottgu/archive/2010/07/16/code-first-development-with-entity-framework-4.aspx

In addition to supporting a designer-based development workflow, EF4 also enables a more code-centric option which we call “code first development”.  Code-First Development enables a pretty sweet development workflow.  It enables you to:

    • Develop without ever having to open a designer or define an XML mapping file
    • Define your model objects by simply writing “plain old classes” with no base classes required
    • Use a “convention over configuration” approach that enables database persistence without explicitly configuring anything
    • Optionally override the convention-based persistence and use a fluent code API to fully customize the persistence mapping
0
 
Robb HillSenior .Net DeveloperAuthor Commented:
Thanks for your advice.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now