One big thing to watch out for is GC differences. Now that Mono has sgen the gap between it and MS's CLR isn't so huge, but you will definitely want to do some memory and CPU profiling direct on the webserver to spot any issues.
In my case when rolling out the JSIL compiler (mostly C#, but using some F# applications as test cases etc) certain BCL containers had dramatically different GC pressure profiles, and GCs would trigger at different rates and with different costs. F# tends to generate a lot of GC pressure so you want to be proactive about this.
Side-by-side, though, sgen works pretty well. I've used it extensively and it does the job.
Comments
One big thing to watch out for is GC differences. Now that Mono has sgen the gap between it and MS's CLR isn't so huge, but you will definitely want to do some memory and CPU profiling direct on the webserver to spot any issues.
In my case when rolling out the JSIL compiler (mostly C#, but using some F# applications as test cases etc) certain BCL containers had dramatically different GC pressure profiles, and GCs would trigger at different rates and with different costs. F# tends to generate a lot of GC pressure so you want to be proactive about this.
Side-by-side, though, sgen works pretty well. I've used it extensively and it does the job.