Because my project use EF core 2.2. LINQPad is a very convenient tool help me to develop efficiency. I used LINQPad5 for a while, because 5 doesn’t support builtin EF core connection so I use my custom domain.dll that running on the EF core 2.2. I need to rebuild the domain.dll when my entity changed or add some new entities. The LINQPad6 builtin EF core connection is nice to me, but the 3.0 behavior is not same with 2.2. So I’d like to use EF core 2.2.
Comments
Because my project use EF core 2.2. LINQPad is a very convenient tool help me to develop efficiency. I used LINQPad5 for a while, because 5 doesn’t support builtin EF core connection so I use my custom domain.dll that running on the EF core 2.2. I need to rebuild the domain.dll when my entity changed or add some new entities. The LINQPad6 builtin EF core connection is nice to me, but the 3.0 behavior is not same with 2.2. So I’d like to use EF core 2.2.
If it's red, LINQPad should use whatever version of EF Core that your project uses.
Can you tell me what happens when you run the following query:
typeof (DbContext).Assembly.GetName()