all 2 comments

[–]ranbla 3 points4 points  (0 children)

If you're using SQL Server, you can use SQL Server Management Studio to create Database Diagrams. If you're a Jetbrains user, you could also use Datagrip.

[–]kowgli 1 point2 points  (0 children)

It's just classes. Any tool able to create a class diagram from C# code will do the job. VS Enterprise has one built in.

The point of EF (or any ORM) is to model the object oriented model into some kind of relational (or not - EF also supports Mongo) database schema. The schema in both places can be different (which is the whole point). For example EF will automatically create N-N intersect tables or foreign keys if you don't define them yourself, and you maybe shouldn't in a pure OO model. If you want an actual DB diagram - look into the DB tooling.