Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
EF Core 3.1: New Overrides
See original GitHub issueProtip: When supporting EF Core 3.1, mocked DbSet<> objects need to additionally override the newly-added methods .AsQueryable() and .AsAsyncEnumerable() (which simply return this;) within BuildMockDbSet() calls.
Anyone who (like me) was using the .AsQueryable() extension method upon a DbSet<> in production code will, after upgrade to 3.1, be calling the methods upon DbSet<> instead. In my case, this meant that instead of getting a cast of the DbSet<> to IQueryable<> I was getting an auto-generated default implementation from Moq’s DefaultValueProvider, which is basically Array.Empty<T>.AsQueryable().
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@likemike91 Created a new ticket and PR. Hopefully we can get this fixed 👍
Is that also fixed for NSubstitute? Unfortunately I get the same error when using NSubstitute and I didn’t see the fix in the code of the NSubstitute extension?