Related to discussion: https://efreversepoco.codeplex.com/discussions/568503
I would like to move this as an issue because IDbSet is a deprecated interface, and this api will not be updated anymore, so any new functionality will not be added in the IDbSet, but only in DbSet, like the "AddRange":
Took directly from the IDbSet official code comments:
"
IDbSet<TEntity> was originally intended to allow creation of test doubles (mocks or fakes) for DbSet<TEntity>. However, this approach has issues in that adding new members to an interface breaks existing code that already implements the interface without the new members. Therefore, starting with EF6, no new members will be added to this interface and it is recommended that DbSet<TEntity> be used as the base class for test doubles.
"
Testing with a mocking framework (EF6 onwards): https://msdn.microsoft.com/en-us/data/dn314429
Testing with your own test doubles (EF6 onwards): https://msdn.microsoft.com/en-us/data/dn314431
Comments: This is now implemented, and will be in the next release.
I would like to move this as an issue because IDbSet is a deprecated interface, and this api will not be updated anymore, so any new functionality will not be added in the IDbSet, but only in DbSet, like the "AddRange":
Took directly from the IDbSet official code comments:
"
IDbSet<TEntity> was originally intended to allow creation of test doubles (mocks or fakes) for DbSet<TEntity>. However, this approach has issues in that adding new members to an interface breaks existing code that already implements the interface without the new members. Therefore, starting with EF6, no new members will be added to this interface and it is recommended that DbSet<TEntity> be used as the base class for test doubles.
"
Testing with a mocking framework (EF6 onwards): https://msdn.microsoft.com/en-us/data/dn314429
Testing with your own test doubles (EF6 onwards): https://msdn.microsoft.com/en-us/data/dn314431
Comments: This is now implemented, and will be in the next release.