Closed eerhardt closed 9 months ago
I am incredibly biased here, since I am the author of MySqlConnector, but I would strongly advocate for https://www.nuget.org/packages/MySqlConnector/ to be the preferred library for MySQL. Some reasons:
DbBatch
, DbDataSource
, and other new ADO.NET abstractions that have been introduced in recent .NET versions; MySql.Data does not.I'm sure Aspire could have components for both MySqlConnector and MySql.Data, but if it's going to be an "opinionated stack" (emphasis in original), I know which opinion I want it to have. 😀
Re-opening to track adding an EF based component.
Putting this in preview2 but it'll likely make it for preview3 unless @bgrainger can get this done before next Tuesday 😄
This appears to be in.
Per https://github.com/dotnet/aspire/issues/786#issuecomment-1817404908 it's not done, as the MySQL EF Core component (Pomelo) isn't in yet.
I'm assuming the EF Core component is tracking a later preview now?
We will probably have both EF and non-EF components (just like the other database components).
https://www.nuget.org/packages/MySql.EntityFrameworkCore https://www.nuget.org/packages/MySql.Data