The Microsoft.FSharp.Compiler.Silverlight DLL has a class that lets you create a hosted F# Interactive session. This adds that capability to the .NET 4.0 build.
…trol-n (F# uses decimals, not octals), and make control-d delete char when not at the end
Binaries built by msbuildd and xbuild now go in lib/release/4.0/... etc. as described in the README
Mono 2.1 profile does not have DebuggerBrowsable attribute. This means wwe currently give an invalid FSHarp.Core.dll for Mono 2.1 profile. Suppress the generation of DebuggerBrowsablee if the attribute does not occur in mscorlib.dll
On mac this now reports the following more helpful message: configure: WARNING: /usr/local/bin/mono not found. Prefix should normally be set to the mono installation path. Please re-run with ./autogen.sh --prefix=/Library/Frameworks/Mono.framework/Versions/3.0.1
The FSStrings.resources was being dropped. This is because of differences in resource file processing for MSBuild and XBuild. This detects which is being used and adjusts resource file processing accordingly.
This includes adding dependencies for the Mono profile 2.1 binaries we need to reference
In case you need a clarification wrt bloat: http://tirania.org/blog/archive/2012/Oct-20.html
See #50 The comments in FSharpBuild/Fsc.fs explain a bit more. It is realy hard to work out how to make this perfectly consistent. Essentially, be careful using resources in folders if you want your projects to be portable across VisualStudio/MSBuild and mono/MonoDevelop/XBuild We hit this bug in fsharp/fsharpbinding, but we've moved that to no longer put resources in folders for now.