Skip to main content

Entity Framework 4.1 Problem

One of the great improvements of Entity Framework 4.1 is the introduction of conventions. Unfortunately due to some time constraints the EF team had to remove the support for customizable conventions. Still, there are some default conventions already available.

And it was one of these conventions that bit me in the foot last week. I created the following model:

public class PizzaIngredient
{
public int PizzaIngredientId { get; set; }
[Range(1,10)]
public int Price { get; set; }
[Required]
public string IngredientName { get; set; }
public string Description { get; set; }
}

and the following context:

public class PizzaPlanetMVCContext : DbContext
{
public DbSet<PizzaPlanet.MVC.Models.PizzaIngredient> PizzaIngredients { get; set; }
}

However when running the application, the following error message was returned:

Invalid object name 'dbo.PizzaIngredients’.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Invalid object name 'dbo.PizzaIngredients’.

The reason is that there is a default convention that defines the name of the table by pluralizing the name of the entity(PizzaIngredient –> PizzaIngredients). As I had created my database up front, my table was called PizzaIngredient which of course resulted in an invalid query.

How can you solve this?

The simplest way to solve this, is by removing this convention. Therefore open up the context class and add the following code block:

protected override void OnModelCreating(DbModelBuilder modelBuilder)
{
modelBuilder.Conventions.Remove<PluralizingTableNameConvention>();
}

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...