Such feature officially does not exist currently (EF Core 2.0.2 and also the incoming 2.1). It’s been requested in Eager load all navigation properties #4851(Closed) and currently is tracked by Rule-based eager load (include) #2953 and Allow for declaring aggregates in the model (e.g. defining included properties or by some other means) #1985 (both in … Read more
This is enough if you want to choose a connection string per http request, based on the active http request’s parameters. using Microsoft.AspNetCore.Http; //.. services.TryAddSingleton<IHttpContextAccessor, HttpContextAccessor>(); services.AddDbContext<ERPContext>((serviceProvider, options) => { var httpContext = serviceProvider.GetService<IHttpContextAccessor>().HttpContext; var httpRequest = httpContext.Request; var connection = GetConnection(httpRequest); options.UseSqlServer(connection); }); Update A year or so later, my solution looks like bits … Read more
EF core 5/6 / Net 5/6 query.ToQueryString() See Documentation ToQueryString() and What’s New in EF Core 5.0 var query = _context.Widgets.Where(w => w.IsReal && w.Id == 42); var sql = query.ToQueryString(); For older net core frameworks an Extension can be used. Core 2.1.2 using System.Linq; using System.Reflection; using Microsoft.EntityFrameworkCore.Query; using Microsoft.EntityFrameworkCore.Query.Internal; using Microsoft.EntityFrameworkCore.Query.Expressions; using Microsoft.EntityFrameworkCore.Query.Sql; … Read more
Support for stored procedures in EF Core 1.0 is resolved now, this also supports the mapping of multiple result-sets. Check here for the fix details And you can call it like this in c# var userType = dbContext.Set().FromSql(“dbo.SomeSproc @Id = {0}, @Name = {1}”, 45, “Ada”);
Since I prefer attributes, here the alternative for the sake of completeness: using System.ComponentModel.DataAnnotations; using System.ComponentModel.DataAnnotations.Schema; [Key] [DatabaseGenerated(DatabaseGeneratedOption.None)] public int Id { get; set; } Note: This works also in EF Core.
This is a known Intellisense issue with the ThenInclude overload for collection type navigation properties, tracked by the Completion missing members of lambda parameter in fault tolerance case #8237 Roslyn GitHub issue. Until it gets fixed, simply type the name of the property and it will compile successfully and work as expected. .ThenInclude(mu => mu.ParseSubTrees) … Read more
The reason is explained in the Loading Related Data section of the EF Core documentation. The first behavior is because EF Core currently does not support lazy loading, so normally you’ll get null for navigation properties until you specifically load them via eager or explicit loading. However, the Eager loading section contains the following: Tip … Read more
It depends if you’re using EF Core 2.1 or EF Core 3 and higher versions. If you’re using EF Core 2.1 If you’re using EF Core 2.1 Release Candidate 1 available since 7 may 2018, you can take advantage of the proposed new feature which is Query type. What is query type? In addition to … Read more
Entity Framework core 5 is the first EF version to support filtered Include. How it works Supported operations: Where OrderBy(Descending)/ThenBy(Descending) Skip Take Some usage examples (from the original feature request and the github commmit) : Only one filter allowed per navigation, so for cases where the same navigation needs to be included multiple times (e.g. … Read more