Hi,

We used to run the Nov 2008 CTP on mono (2.2) with no problem. We upgraded to the May 2009 one, and even after getting the latest mono (2.4), we cannot compile anymore. Sample issues look like not finding methods like File.AppendAllContents, or the compiler not being able to find the overload for String.Split(char [], int) and instead offering the other ones as potential overloads:

fsc --target:library --out:MindsetMedia.Utils.dll --debug:full --define:DEBUG --warn:4 --warnaserror+ -r:System.dll ShellParams.fs

Microsoft F# Compiler, (c) Microsoft Corporation, All Rights Reserved

F# Version 1.9.6.16, compiling for .NET Framework Version v2.0.50727

\Users\yves\Sources\Mm\src\mm\metrics_dev\Utils\ShellParams.fs(31,23): error FS0041: No overloads match for method Split. Possible matches are shown below (or in the Error List window)

Possible overload: 'System.String.Split(separator: char []) : string []'.

Possible overload: 'System.String.Split(separator: char []) : string []'.

Possible overload: 'System.String.Split(separator: char [], options: System.StringSplitOptions) : string []'.

Possible overload: 'System.String.Split(separator: string [], options: System.StringSplitOptions) : string []'.

Type constraint mismatch. The type

char array

is not compatible with type

char

The type 'char array' is not compatible with the type 'char'

Type constraint mismatch. The type

int

is not compatible with type

System.StringSplitOptions

The type 'int' is not compatible with the type 'System.StringSplitOptions'

Type constraint mismatch. The type

char array

is not compatible with type

string []

The type 'string' does not match the type 'char'

The code in this example is:

let public ParseShellParam(tokens : string list) : ShellParam =

let p =

match tokens with

| [] -> raise MalformedShellParameter

| one :: [] ->

match one.Split([| '=' |], 2) with

| [| var; value |] -> ShellArg(var, value)

| [| switch |] -> ShellSwitch(switch, [])

| .......... (abbreviated)

Mono is from MacPorts on OS X.

Any idea why this could happen? Has someone else run into this? Are there flags I can use on the command line to see which assemblies the compiler is looking at?

Thanks!