Summary
While CSV, JSON, and XML all have EF Core provider implementations, the XLS (Excel) format has only an ADO.NET provider with no corresponding EF Core support. There is no EFCore.Xls project.
Current XLS ADO.NET State
- Read-only (SELECT only, no INSERT/UPDATE/DELETE)
- No DataAdapter
- Schema detection works
What an EF Core XLS Provider Would Need
XlsRelationalConnectionXlsOptionsExtension + UseXls() extension methodXlsTypeMappingSourceXlsQuerySqlGeneratorXlsDatabaseModelFactory (for scaffolding read-only models)XlsDatabaseCreator (would need to handle read-only limitation)
Considerations
Since XLS is read-only at the ADO.NET level, the EF Core provider would be read-only too. This is valid — some providers are query-only. The provider should:
- Throw clear errors on write operations (
SaveChanges with modifications)
- Support
AsNoTracking() queries efficiently
- Support scaffolding to generate read-only entity models
Priority
Lower priority than completing the CSV/JSON/XML providers, but would provide feature parity.
Summary
While CSV, JSON, and XML all have EF Core provider implementations, the XLS (Excel) format has only an ADO.NET provider with no corresponding EF Core support. There is no
EFCore.Xlsproject.Current XLS ADO.NET State
What an EF Core XLS Provider Would Need
XlsRelationalConnectionXlsOptionsExtension+UseXls()extension methodXlsTypeMappingSourceXlsQuerySqlGeneratorXlsDatabaseModelFactory(for scaffolding read-only models)XlsDatabaseCreator(would need to handle read-only limitation)Considerations
Since XLS is read-only at the ADO.NET level, the EF Core provider would be read-only too. This is valid — some providers are query-only. The provider should:
SaveChangeswith modifications)AsNoTracking()queries efficientlyPriority
Lower priority than completing the CSV/JSON/XML providers, but would provide feature parity.