Скачать или смотреть Issues with .NET Core CLI DbContext Scaffold Naming? Here's the Solution!

Discover how to tackle the issue of singular table names in .NET Core DbContext scaffold after upgrading to .NET 5, along with a quick temporary fix.
---
This video is based on the question https://stackoverflow.com/q/71944826/ asked by the user 'Sean Ad' ( https://stackoverflow.com/u/2741538/ ) and on the answer https://stackoverflow.com/a/71956417/ provided by the user 'Sean Ad' ( https://stackoverflow.com/u/2741538/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: .Net core CLI DbContext scaffold changed table name to sigular

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Issues with .NET Core CLI DbContext Scaffold Naming? Here's the Solution!

Upgrading software often comes with its fair share of complications, and the recent transition from .NET Core 3.x to .NET 5 has presented one notable problem for developers using Entity Framework: the change from plural to singular table names when scaffolding a DbContext from an existing database. If you've run into this problem, you're not alone. This guide dives into the issue and provides you with a reliable workaround until a more permanent fix is developed.

Understanding the Problem

When using the command to scaffold a DbContext, many developers noticed that their mapped classes were generated with singular names instead of the expected plural form. For example, a table named books would now be represented simply as book. This unintended change can create confusion and disrupt projects that rely on consistent naming conventions.

Context of the Issue

The command typically used for scaffolding looks like this:

[[See Video to Reveal this Text or Code Snippet]]

After upgrading to .NET 5, despite the use of options like --use-database-names, developers found that the generated class names remained unchanged. Many users were dissatisfied, particularly those who appreciated the automatically generated column names by Entity Framework.

Temporary Solution

Unfortunately, as of now, the specific issue of altered class name singularization in Entity Framework Core 5.x has been recognized and a fix is on the way. In the meantime, there is a quick workaround that you can implement to restore the expected plural naming convention:

Downgrading Entity Framework Packages

Identify the Packages: If you are facing issues with the class names, consider downgrading the following EF packages:

Microsoft.EntityFrameworkCore.Design

Microsoft.EntityFrameworkCore.SqlServer

Microsoft.EntityFrameworkCore.Tools

Execute Downgrade Commands: You can use the following commands to downgrade these packages from version 5.0.15 to 3.1.24:

[[See Video to Reveal this Text or Code Snippet]]

Check Your Version: After downgrading, you can check the installed versions using:

[[See Video to Reveal this Text or Code Snippet]]

Additional Update

If you updated the CLI tool in an attempt to rectify the issue by running

[[See Video to Reveal this Text or Code Snippet]]

and still didn't observe changes, it's important to note that the updates you performed were to the CLI and not the core libraries.

Conclusion

While the recent upgrade to .NET 5 has led to some frustrations with DbContext scaffolding and singular naming conventions, we hope this workaround gives you a temporary solution to keep your project on track. Stay informed for the upcoming patch that will address this issue directly, and keep an eye on official EF Core channels for further updates.

By downgrading specific packages, you can maintain a consistent naming convention in your entity classes until the broader issues are resolved. Happy coding!