Colin Gravill

I've add the automatic referencing of netstandard in #218 so the highlighting issue should be solved. I'm not sure the right answer about automatically referencing other libraries, it's convenient but...

Btw I also made the Paket helper script work better in netcore, it might help getting the right dlls referenced too.

I gave this a go with the latest and it seems to working for me now:  The error highlighting looks to be a false positive:  Based on this...

Yes, I'm very hopeful about that change to #r. We could also potentially just use FAKE's current syntax which implements an approximation to it: https://github.com/fsprojects/IfSharp/issues/112#issuecomment-504662581 which now supports unmanaged references...

There's a bit of a mismatch between the editor services and execution engine on Linux causing this. I don't recall if it's now fixed in master but the Docker image...

It's not a .NET Core issue. I'd be tempted to just initialise as a seq or convert to that: ```fsharp [ {|id=5; name = "hello"|} ] |> Seq.ofList |> Util.Table...

To confirm the implicit conversion works for explict records:  https://github.com/fsprojects/IfSharp/blob/5a415a7618ce91c41ba441688db29fbaa8d03410/src/IfSharp.Kernel/Util.fs#L86-L100

That would be great. It's a VM currently. Would we need create a service principal on the container registry? Doing this with Farmer is very new to me (but pleasant)...

Thanks @ninjarobot that's incredibly helpful - particularly the roleAssignment. That should remove the need for my generated PowerShell. Will try and let you know how it goes. We're already creating...

I've now integrated this general approach into our deployment, it's working great, thanks @ninjarobot