Resolve ambiguous type definitions
See original GitHub issueThe problem is that in one of the databases I want to reverse engineer, there is a table called EventHandler. So the created model for the entity is called EventHandler
, which conflicts with the System.EventHandler
. I would have to resolve this problem manually every time EF scaffold is executed. For now, this is not a huge problem because I just have to add the line
using EventHandler = Database.Models.EventHandler;
But if this would not be the only entity then this could get an annoying problem. So is it possible to automatically specify the whole type name including the namespace to resolve ambiguous type definitions?
Further technical details
EF Core version in use: EF Core 5
Is Handlebars used: no
EF Core Power Tools version: 2.5.908.0
Database engine: SQL Server
Visual Studio version: VS 2019
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (8 by maintainers)
Top GitHub Comments
Keep in mind that this is free open source software.
If you use Handlebars you can add this to the top of all files, maybe conditionally
I’m asking for an automated fix which is not the renaming feature. If there is one pls tell me because currently, I have to do it manually. That’s what the issue is about