We're happy to use your library and really like it!
We use the .net framework 2.2.0 (fixed) and your library in 0.3.10 which has a dependency to Microsoft.EntityFrameworkCore.Design >= 1.0.1.
You added a fix since this version regarding transactions and we're in urge to get this fix, but sadly you changed the dependency to Microsoft.EntityFrameworkCore.Design >= 2.2.6.
Is this update really required? Could you "downgrade" the requirement to >= 2.2.0?
We wan't to update the EF framework but it's impossible for the coming months. Downgrading the requirement wouldn't hurt your library anyway.
Just as a note:
When publishing a package try to stick to the lowest dependencies possible (or none at all, obviously) to increase the adaption rate. 👍
Hi!
We're happy to use your library and really like it! We use the .net framework 2.2.0 (fixed) and your library in 0.3.10 which has a dependency to
Microsoft.EntityFrameworkCore.Design >= 1.0.1
. You added a fix since this version regarding transactions and we're in urge to get this fix, but sadly you changed the dependency toMicrosoft.EntityFrameworkCore.Design >= 2.2.6
. Is this update really required? Could you "downgrade" the requirement to>= 2.2.0
? We wan't to update the EF framework but it's impossible for the coming months. Downgrading the requirement wouldn't hurt your library anyway.What's you opinion about that?