Arthur Vickers

@divega I was just thinking I needed to file this! :-) What do you think about depending on the new package (and only the new package) for .NET Core, and...

We decided that the existing provider will continue to use `System.Data.SqlClient`, which is non-breaking. However, we will likely release a new provider that uses `Microsoft.Data.SqlClient` at some point post 6.3,...

@CZEMacLeod The existing provider will still be in-the-box. We aren't changing that.

@dmmusil @CZEMacLeod It will likely multi-target .NET Framework and .NET Standard 2.1, like the existing provider. When/if we do that will depend mostly on adoption of EF6 on .NET Core....

We're planning one for later in the year, so we can do it then.

@bricelam Would we expect an `app.config` in a `netcoreapp3.0` class library to be picked up? More generally, do we have docs (or issues tracking docs) to help understand `app.config` in...

@bricelam Assigning to you to investigate. From my testing, everything is working when the code is executed in the normal way, but it's not getting picked up by the migrations...

This issue has been closed because EF6 is no longer being actively developed. We are instead focusing on stability of the codebase, which means we will only make changes to...

This PR has been closed because EF6 is no longer being actively developed. We are instead focusing on stability of the codebase, which means we will only make changes to...

@jkotas @roji Does anything need doing here?