Tuomas Hietanen

Hi, I just updated the package to contain System.Data.SqlClient of package 4.8.0 Hopefully helps. @jl0pd just a guess, sounds like your compile-time version of System.Runtime.dll doesn't match the execution time...

System.Data.SqlClient are one of the few which are currently not loaded via reflection...

I think it's version 4.6.1? Or 4.8? Is there a problem? Do you do binding redirects?

I think I updated it to 4.8, but I may have missed something. https://github.com/fsprojects/SQLProvider/blob/4d79debfc59fbba1e3fae1e816d1d9309bbfe012/paket.lock#L152

I was planing to use FSharp.Compiler.Tools because people have here lot of compilation issues and some of them come by using wrong fsc.exe, so I thought maybe the compiler tools...

@njeisecke, I'm confused... I thought type providers still need Mono to compile. Has this changed with .NET Core 3.1?

> Type Providers have not needed mono to compile for quite a long time. Wow, cool. :-D All these undocumented features that I'm not aware of.

This is possible duplicate of #585

But also if you plan to catch/continue on error you probably then want to do `.ClearUpdates()` (and maybe error handling/logging for that?) for the context so that it won't fail...

I bet this is a design decision that you don't have to catch everything, instead on failure you can get the pending updates from `.GetUpdates()` if you want, or you...