Proposal - prioritize finishing v9 and v10; remove compiled-models work

[lorcQc]

Hi all,

Short summary: we’re currently behind on EF Core 9 support and EF Core 10 was released last week... I propose temporarily removing the compiled-models work so we can finish v9, then start work on v10.

Current status (v9)

• We dont yet have a version that can be compiled with EF Core 9.
• Migrations (Add-Migration): Mostly implemented — generates VB migration files that record model changes.
• Scaffolding (Scaffold-DbContext): Mostly implemented — reverse-engineers a database into VB DbContext and entity classes.
• The main remaining work is the compiled models feature (Optimize-DbContext).

The compiled-models work consumes a large portion of my maintenance time and I don't know if anyone relying on it, Also, let's just say that its implementation requires the use of internal EF Core components that are designed more for performance than to be CLS compliant.

Proposal

• Remove the compiled-models code path from the active code base.
• Finish v9 (migrations and scaffolding).
• Start work on EF Core 10 support and publish v10 as soon as possible.

[InteXX]

I propose temporarily removing the compiled-models work so we can finish v9

Are they in their own branch?

I'd like to do what little I can to help, but I'm not sure where to begin. Any suggestions?

[lorcQc]

Hello @InteXX ,
Thank you for offering your help.
Unless there are any surprises, the work should be straightforward, i.e., reproducing the changes made to the C# files in the official repository.
I'm finishing v9 and then, if you're interested, I'll get back to you with the details of what needs to be done.

[InteXX]

Yes, please do.