Scaffolding fails if model class is in a dependency (project/ library) of the project on which scaffolding is being run.
See original GitHub issueIssue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:35 (7 by maintainers)
Top Results From Across the Web
Scaffolding fails if model class is in a dependency (project ...
Scaffolding fails if model class is in a dependency (project/ library) of the project on which scaffolding is being run. #251.
Read more >multiple types matching the name while Scaffolding ASP. ...
Scaffolding fails if model class is in a dependency (project/ library) of the project on which scaffolding is being run. #251.
Read more >Scaffolding Error when Model and DbContext are in ...
4.1 and entity framework core 2.0 fails when my model and data classes are in separate class libraries. I have a Portal MVC...
Read more >Fix Update: Scaffolding failed, could not load information for ...
Fix Update: Scaffolding failed, could not load information for project | Visual Studio | Updated. 5.3K views · 10 months ago ...more ...
Read more >.NET Identity Scaffolding Error - YouTube
NET Identity Class Library for Authentication. ... (in cases when you have multiple project and references as seen here .
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Still, exists.
Thanks @Vikaskumargd, The problem is with the DbContext being in the library, not the model classes. The DbContext in libraries isn’t supported fully because editing it is not possible, however, it is possible to make it work if no edits are needed. I have filed https://github.com/aspnet/Scaffolding/issues/365 to enable this scenario. As a workaround for now, you can try to move the DbContext to the main project.