JoeAlbahari

Also note that when you create the connection in LINQPad 6, you have the option of choosing EF Core instead of LINQ-to-SQL. If you choose EF Core, you'll be able to call this.Database.ExecuteSqlInter… (View Post)

This is a good use-case. I will be adding explicit support for xunit soon, to make this easier. (View Post)

LINQPad supports lazy loading with EF Core, and always has. Are you using a DbContext defined in your own assembly? If so, you must enable lazy loading in the OnConfiguring method: protected override… (View Post)

The behavior makes sense, because LINQPad installs its DbCommandInterceptor first. You can tell LINQPad not to write SQL translations by doing this in your setup code: ExecutionEngine.SqlTranslations… (View Post)

I'm not sure that we need an option - can you think of any reason why unsafe shouldn't just be the default? (View Post)