Contents tagged with ADO.NET

  • Best Decision to Kill LINQ to SQL

    I fully agree with Tim Mallalieu to recommend LINQ to Entities as the data access solution for your application. Sure, for an object-oriented view of the database LINQ to SQL was somewhat useful but in essence this is a scenario that the Entity Framework supports as well. Yes, in some ways the Entity Framework does add a bit of complexity but then again creating a direct mapping with the Entity Framework isn't much more difficult then it would be with LINQ to SQL. Apart from the fact that Microsoft shouldn't have released LINQ to SQL as a product I was quit surprised about the wave of people adopting this piece of technology. A tool for direct mappings misused as an object-relational mapper felt awkward from the start. I hoped for a little while that LINQ to SQL would evolve in a fully fledged object-relational mapper, but the Entity Framework with it's EDM investment had more potential from the start.

  • EDM Designer Quirks

    Don't be fooled with the EDM designer in SP1 beta for VS.NET 2008. Apparently there was no need "yet" for in depth customizability of the store model schema. For my class table inheritance example I'm using table prefixes since I'm running many examples on the same database. The prefix I'm using for this example is cti_ as you might have guessed. Everything works as you would expect until you try to write a linq to entities query. Instead of writing:

  • Entity Framework for Domain Model based Application Architectures

    I am sitting here listening to the MSDN Webcast: Framework Masterclass: LINQ to Entities and guess what. Patrick Lowendahl is there as well and beat me to it with the following remark.

    Question: Eilsa, if you want more feedback from DDD mvps you can drop me or my friend Jimmy (who wrote the second book, and only .net book, on the subject) a line

    Excellent! Wouldn't it be great to use the Entity Framework for our domain model based application architectures. My question in this particular area:

    Question: What improvements can we expect in the designer?
    Answer: The current designer is actually a CTP 1 that works with the Beta 2 of the EF. We are currently working hard to implement customer feedback and implement things such as the model first scenario. You should see significant changes in the designer coming soon.

  • ADO.NET Entity Framework June CTP

    For those of you who have been living under a rock, here is the ADO.NET team announcement of fresh bits of next generation data access stuff. To be honest I'm really glad that the team found another release vehicle. A lot of people I've been talking to lately made it very clear to me that they have lost hope and repeatedly tried to remind me of previous failures. Let's hope for the best!

  • RAD is Making a Comeback with Jasper

    Andrew Conrad announced project "Jasper" earlier this week at Mix '07. Jasper is different from typical O/R frameworks that often require data classes to be written by hand, or generated at development-time using a tool. Jasper on the other hand connects to the database, determines the database schema, and generates the corresponding data classes. The interesting thing is that this generation does not result in source files. The data classes are compiled in-memory and are available within the running program. If the database schema changes from run to run, the dynamically generated data classes reflect the schema changes without any developer intervention. See the Microsoft Codename Jasper CTP Overview document in the CTP for more details.