Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Scaffold-DbContext can name namespace wrong if phrase with space is used on OutputDir
See original GitHub issueScaffold-DbContext is naming namespace wrong if -OutputDir is filled with phrase containing space.
For example: Example Folder OutputDir makes namespace ConsoleApp.Example Folder, what is wrong for naming namespaces and can’t be builded. It should be ConsoleApp.Example_Folder.
Code
I made command through PMC like this:
Scaffold-DbContext "connectionString" MySql.EntityFrameworkCore -Tables some_tables_here -OutputDir "Example Folder" -Force
Command is working, but output classes and context have wrong namespace.
Include provider and version information
EF Core version: 5.0 Database provider: MySql.EntityFrameworkCore Target framework: NET 5.0 Operating system: IDE: Visual Studio 2019 16.9.3
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes, I’m OK with this approach. It would also be nice to do it for Migration class names.
I encountered the same issue when using a dash “-” in the output directory name. All the namespaces get invalid names and the classes wont build.