entity-framework-core

I have a DefaultAttribute defined like so: [AttributeUsage(AttributeTargets.Property)] public class DefaultAttribute : Attribute { /// <summary> /// Specifies this property has a default value upon creation. /// </summary> /// <param name="defaultValue">The default value of the property.</param> /// <param name="useAsLiteral">Set to true if the value is <em>not</em> quoted in the DDL.</param> public DefaultAttribute(object defaultValue, bool useAsLiteral = false) { DefaultValue = defaultValue; UseAsLiteral = useAsLiteral; } public object DefaultValue { get; private set; } /// <summary> ///

I want to use LinqKit's PredicateBuilder and pass the predicate into .Any method for related model. So I want to build a predicate: var castCondition = PredicateBuilder.New<CastInfo>(true); if (movies != null && movies.Length > 0) { castCondition = castCondition.And(c => movies.Contains(c.MovieId)); } if (roleType > 0) { castCondition = castCondition.And(c => c.RoleId == roleType); } And then use it to filter model that has relation to model in predicate: IQueryable<Name> result = _context.Name.AsExpandable().Where(n => n.CastInfo.Any(castCondition)); return await result.OrderBy(n => n.Name1)

EF Core 1.1 and SQL Server 2016 We are running a microservice application with some microservices having independent few tables. One of the solutions to have many tables for individual microservice, is to give these services a unique schema (e.g. not DBO) and put all of them in one database (good for cost + maintenance). That works fine in EF 6, however, looking at the generated dbo.__EFMigrationsHistory in core, it looks like core doesn't take the schema into account. I am aware that the migration in EF Core has changed to look in the code rather than the DB, but my problem is the version

I try to test my app so I need to mock my EF context. My code seems to be ok, but I have following exception: "System.ArgumentNullException : Value cannot be null. Parameter name: source" Here is my test method: var options = new DbContextOptionsBuilder<ProductContext>().Options; var settings = new SqlSettings { InMemory = true }; var context = new Mock<ProductContext>(options, settings); var mockTreeService = new TreeService(context.Object); await mockTreeService.CreateTreeAsync("Testing tree", Guid.NewGuid()); context.Verify(x => x.AddAsync(It.IsAny<Tree>(), CancellationToken.None), Times

As noted in "Loading Related Data" from EF Core Documentation we can use .Include(..) to Eagerly Load navigation properties from the DbSet (or generic IQueryable<T> linking back to an EF context). This means that, given the following models: public class TestEntityA { public int Id { get; set; } public int TestEntityBId { get; set; } public TestEntityB TestEntityB { get; set; } public string BProperty { get { return TestEntityB.Property; } } } public class TestEntityB { public int Id { get; set; } public string Property { get; set; } } .. then code such as the following should work: context