Mikayla Hutchinson

@mrward where do I need to wire the option in? I'm finding it hard to unwind all the layers of abstractions in the PackageManagement code.

(test failures are unrelated)

Remaining failures appear to be brokenness in the actual templates, e.g. ``` [("Build error", "/Users/mikayla/code/monodevelop/main/tests/tmp/fsharp-buildtemplates/Xamarin.iOS.FSharp.SingleViewApp/FSC", "The type 'BigInteger' is required here and is unavailable. You must add a reference to...

I'm going to start cherry-picking off some of this F# stuff into separate PRs.

OK, merged F# fixes to master and rebased this onto master 🤞

4 of the remaining 6 failing tests have the following issue: `"Package Xamarin.Android.FSharp.ResourceProvider 1.0.0.25 is not compatible with monoandroid90 (MonoAndroid,Version=v9.0). Package Xamarin.Android.FSharp.ResourceProvider 1.0.0.25 supports: net (.NETFramework,Version=v0.0)"` @nosami can we update...

The other two fail with ```"Version conflict detected for Xamarin.Android.Support.Compat. Reference the package directly from the project to resolve this issue. \n Xamarin.Forms.FSharp.FormsApp.Droid (>= 1.0.0) -> Xamarin.Android.Support.v4 (>= 27.0.2) ->...

@mrward F# tests are failing with this error in NuGet restore, any ideas? ``` 2019-07-30T23:05:11.4869760Z 5) MonoDevelop FSharp LibraryProject (MonoDevelopTests.Template tests.MonoDevelop FSharp LibraryProject) 2019-07-30T23:05:11.4870100Z System.AggregateException : One or more errors...

(this is also a horrible stack track and should probably be cleaned up with sole judicious catches and flattening)

Yeah, it's definitely a regression - when I last looked at this a year ago, only 6 F# tests were failing, and that was due to brokenness in the F#...