You couldn't do it in earlier versions of Entity Framework but, in more recent versions, you can use lambda expressions to save yourself from some runtime errors.
The CQRS pattern separates updates from queries, allowing you to create the best process for each of those activities. Effectively, CQRS codifies the standard practice for ASP.NET MVC developers: Here are some strategies for implementing that pattern and improving your application's performance.
New version allows for visual design and code generation of apps using Microsoft's newest Entity Framework Core 1.0, as well as popular data access framework from Telerik.
- By Michael Domingo
- 06/02/2016
Providers for Oracle, MySQL, PostgresSQL, SQLite 5.5, and DB 2.0 can now work with Entity Framework Core 1.0 RC1.
- By Michael Domingo
- 04/28/2016
You want to give the user the ability to select one (or more) items from a table. It's not as easy in ASP.NET MVC as you might like... but it's not awful, either.
ASP.NET 5.0 is no more, at least by name -- it's now ASP.NET Core 1.0. Newer versions of .NET Core 5 and Entity Framework 7 will also follow suit.
- By Michael Domingo
- 01/20/2016
EF7 Beta 6 adds data annotations, customization of reverse engineer via templates, and support for raw SQL commands.
- By Michael Domingo
- 07/28/2015
Stored procedures can speed up your code by reducing trips to your database -- even if you only have one SQL statement to execute. Here's how to speed up your application (and how to simplify your stored procedure code).
You don't have to give up on creating dynamic queries just because you're using Entity Framework. Entity SQL and ObjectQuery will let you generate queries at runtime and still let you update your data through Entity Framework.
Version 6.1.2 contains some high-priority fixes that need to be tested in the wild before it is RTM'd; meanwhile, next version of Entity Framework might be version 7 or something else.
- By Michael Domingo
- 11/18/2014
Peter returns to improve performance by splitting a single table into multiple entities, but this time, he implements his solution using the Entity Framework 6 designer.
There are some occasions when using Entity Framework can really hurt you: When you have tables with hundreds of columns or tables with large payloads. Here's how to get EF6 to do the right thing.
Here's an article about managing transactions that you don't need to read because, with one exception, Entity Framework will do the right thing by default. But, in the .NET Framework 4 and later, you can do more (if you ever need to).
You can completely disconnect your test code from your database with Entity Framework 6 in .NET and Visual Studio. You just need a little bit of custom code for your application, along with some boilerplate code.
Thinking in terms of layers or tiers really isn't much help to you. Stop doing it: The single responsibility principle and design patterns are all you really need.
Entity Framework 6 gives you a variety of ways to call stored procedures that return data and capture the results those procedures return. Here's a look at all of them.
Even in a Code First environment, you can call a stored procedure from a DbContext object. But it's a lot easier if you use the visual designer.
Complex Types let you reuse structures in your database design. But unless you've been very lucky around the names in your database, you probably couldn't use Complex Types -- until Entity Framework 6, that is.
The latest version of Entity Framework makes it easier to write asynchronous code. Here's how to write that code, and more important, where you'll actually find it useful.
The latest version of the technology works fine with the Microsoft .NET Framework 4 and Visual Studio 2010. Here's some of what's new (along with how to move your applications to EF6).