Rudi Horn

>would be nice to have I mainly just wanted to hear that it isn't a bad thing to do. I would be interested in implementing this, so I will try...

Could it be this reference is just stale? Have you tried running `Paket.Clear ()` first? With the latest patch I don't get the `System.ComponentModel.Composition` error, and even if I force...

Intellisense hints at: >A reference to the type 'System.Data.Common.DbConnection' in assembly 'netstandard' was found, but the type could not be found in that assembly

I've been wanting to also try debugging which libraries are loaded, but trying to access `System.AppDomain.CurrentDomain` yields the error: >The value, namespace, type or module 'AppDomain' is not defined.

Hmm let me double check this is not actually related to version incompatability. > > > Good reminder on Paket.Clear() but no change there. It might be a operating system...

@cgravill so it seems that the issue is related due to lazy loading of libraries. Initially none of the libraries are in the current AppDomain, and simply using `#r` does...

The complaint about `netstandard.dll` is a bit more worrying, as it refuses to load the netstandard library when you try to force load it. I'm assuming this is an issue...

Yes and interestingly it is actually possible to execute code such as:  It is more the library implementation that is causing issues.

The main difference I can see between `fsi.exe` and IfSharp is that `fsi.exe` calls `FsiEvaluationSession.GetDefaultConfiguration` with `useAuxLib=true`, while IfSharp sets it to false. Setting it to true in IfSharp causes...

>Does the type provider work correctly in an F# Interactive session outside of IFSharp? My understanding is that each of the parts is only recently working on .NET Core. Turns...