Why is Asp.Net Identity IdentityDbContext a Black-Box?
There is a lot of confusion it seems around IdentityDbContext.
There is a lot of confusion it seems around IdentityDbContext.
Below is the kind of test that is failing upon .ShouldNotThrow() due to .ToListAsync() not being supported by in-memory dbsets (I don’t have the exact wording handy but you get the picture). In case it’s of any importance, I’m trying to mockup the dbset provided by Entity Framework ver. 6.1.3:
It seems weird that I couldn’t find an explanation of the difference between those two helpers, so I would assume that is something obvious but I missed.
MVC4 + Entity Framework 4.4 + MySql + POCO/Code First
Dates in my database are stored as Utc. But when I retreieve them w/ the entity framework they come out as type unspecified.
I installed the beta 2 of Visual Studio 2010 today. I went to test out the new entity framework stuff (to see if my “issues” from v1 were fixed.).
Why is this happening when we make a call to the AccountApiController.Register() method?
I have a table called Products which obviously contains products.
However, I need to create related products. So what I’ve done is create a junction table called product_related which has two PKs. ProductID from Products table and RelatedID also from Products table.
I have a many-to-many relationship defined like so:
I have declared the following model using the EF Core fluent API: