The ADO.NET team has released an update along with Beta 2 of .NET 4.0 and Visual Studio 2010. From the looks of it, they got a lot of nifty features in there, obviating the need for an out-of-cycle CTP. Having briefly scanned the list, what stands out to me is the foreign key support (now the default for entity relations), the improvements to POCO, and generation of complex types from stored procedures. I can hardly wait to dig in … I just wish I weren’t so busy!
Categories
-
Join 1,047 other subscribers
Tags
- .NET Core
- .NET Standard
- Angular
- Apple
- Architecture
- ASP.NET-CORE
- ASP.NET-MVC
- Async
- AWS
- Azure
- BDD
- C#
- CLR
- CQRS
- Dapr
- DDD
- Delegates
- DI
- Docker
- Entity Framework
- Entity Framework
- Event Driven
- Events
- Git
- Kafka
- Linux
- MEF
- Microservices
- MOQ
- MVVM
- N-Tier
- Nano Server
- Nginx
- Nin
- Ninject
- NLog
- NUGET
- OData
- OSS
- PCL
- REST
- RIA Services
- Security
- Silverlight
- SOAP
- SpecFlow
- SSL
- Tools
- Trackable Entities
- TypeScript
- Visual Studio
- VSCode
- WCF
- Web API
- WP7
- WPF
-
Recent Posts
Personal
Technical
Twitter
- Listening to @ahejlsberg never gets old. Here’s a fun stroll down memory lane from Turbo Pascal to Delphi to C# to… twitter.com/i/web/status/1… 4 months ago
- RT @davidfowl: "Blazor / C# is the target language for those without a need to know the technical details of WebAssembly" https://t.co/JYR… 5 months ago
- I would like to share that I am starting a new role as Chief Technology Architect for @Hiltigroup F&P Solutions.… twitter.com/i/web/status/1… 6 months ago
Tony Sneed's Blog 
Hi Tony,
I’ve been carrying around the Dec 2008 MSDN magazine for many months referring to your excellent article “SOA Data Access”. I am a part-time programmer who likes to stay as current and adopt the latest technologies, but I have been challenged by EF. I can’t ever get an update to work, even when I closely copy your example code. L2S is easier. But, over time, I came to realize that the lesson of your article is that the data access method doesn’t matter much. It’s the POCOs. In which case I may as well stick with what I’ve been using and know well. ADO.Net. (Maybe they’ve fixed EF in v4, but I regret all the frustration I have endured so far in EFv1. I wish they wouldn’t release stuff until it’s ready.)
Hello Burton,
Thans for sharing your experience with EF v.1. You’re certainly not alone in your frustraions, but I would encourage you to give EF 4.0 a chance. In order to use ADO.NET in an SOA app, you’d probably end up writing your own mapper, which L2S and EF have already done for you. EF 4.0 removes all the obstacles you had to overcome with the prior version when writng n-tier apps. I’m about to write a post on self-tracking entities, but they make n-tier development with EF much easier. EF 4.0 will be released with .NET 4.0 in March 2010.