3 ms·

I'm in the middle of a project that uses.NET Core. It's been great so far but Microsoft is in the middle of changing the tooling for it, which is a major pain p

I'm in the middle of a project that uses.NET Core. It's been great so far but Microsoft is in the middle of changing the tooling for it, which is a major pain point right now. They are essentially changing the project file format that defines dependencies and build options, and SDK tools and IDEs don't all support both formats yet. .NET Core has almost all of the features of the full .NET framework and C# is a pleasure to work with. My team is very productive and we are able to iterate very quickly. Since it is a compiled language, most errors are caught at build time. Deploying is another pain point. You have to install the framework on Linux and ship all of your dependencies. They make it easy with the `dotnet publish` command. I'm excited for .NET Native which will package everything into a binary.

sAbakumoff 10y ago
Do you experience any obstacles with data providers implementation in .NET Core? I heard that they ported SQLDataProvider only.
- caleblloyd 10y ago
  Yes, we did experience obstacles. I wanted to use MySQL for our project and there was no GA Entity Framework implementation when we started. Oracle is way behind the ball on an official driver and their license (GPLv2) is super restrictive. I found `Pomelo.EntityFrameworkCore.MySql` to be a pretty good implementation and started contributing. We ported it to use `MySqlConnector` as a base MySQL driver. Both libraries have matured a lot, are MIT Licensed, optimized for performance, and are now used in production. I think that PostgreSQL has a similar open source story. There's `Npgsql` for a driver and `Npgsql.EntityFrameworkCore.PostgreSQL` for the Entity Framework implementation. It took some work, but I like that Entity Framework Core allows for it's implementations to be done by the Open Source community. In MySQL's case, we've added lots of MySQL-specific optimizations to the Entity Framework implementation after getting feedback from the community. The new open Microsoft development approach here is great.

sAbakumoff 10y ago

Do you experience any obstacles with data providers implementation in .NET Core? I heard that they ported SQLDataProvider only.

caleblloyd 10y ago
Yes, we did experience obstacles. I wanted to use MySQL for our project and there was no GA Entity Framework implementation when we started. Oracle is way behind the ball on an official driver and their license (GPLv2) is super restrictive. I found `Pomelo.EntityFrameworkCore.MySql` to be a pretty good implementation and started contributing. We ported it to use `MySqlConnector` as a base MySQL driver. Both libraries have matured a lot, are MIT Licensed, optimized for performance, and are now used in production. I think that PostgreSQL has a similar open source story. There's `Npgsql` for a driver and `Npgsql.EntityFrameworkCore.PostgreSQL` for the Entity Framework implementation. It took some work, but I like that Entity Framework Core allows for it's implementations to be done by the Open Source community. In MySQL's case, we've added lots of MySQL-specific optimizations to the Entity Framework implementation after getting feedback from the community. The new open Microsoft development approach here is great.