Home

EP Finder — Entity Platform Finder

DotOrgProjects.EntityPlatform.Finder

How many DbSet<T> properties have you declared by hand? EP Finder discovers them automatically, by convention, with no boilerplate.

---

The Problem

In EF Core, the developer must explicitly declare each entity in the DbContext. EP Finder replaces that internal mechanism with automatic discovery based on the [Table] attribute, eliminating the need to maintain one DbSet<T> per entity.

Without EP Finder vs With EP Finder

	Without EP Finder	With EP Finder
Entity registration	Manual — one DbSet<T> per entity	Automatic via [Table]
Custom DbContext	Required	Not required
Boilerplate	High — grows with the model	Minimal — just UseFinderIn()
Discovery	Explicit in DbContext	By convention (namespace)
EF Core support	Native ✓	Native + EP Finder ✓

Conclusion

EP Finder does not replace EF Core — it extends it. If you already use EF Core with Data Attributes, EP Finder eliminates the maintenance of the DbContext and the manual registration of each DbSet<T>, letting convention do the work.

---

Documentation

• Getting Started
• Configuration
• FAQ
• EP Finder Help