I already answered about VS in the comment.
In terms of .NET compatibility, IronScheme is probably better because it is designed and written in .NET and liberal reuse of existing .NET types.
As for the .NET consumer, IronScheme provides excellent support for most .NET features (such as generics, etc.).
As for the .NET maker, IronScheme is still missing. For example, you cannot create generic methods or classes. Typed fields (by records) were introduced only recently, and even this limits a little (there is no support for the definition of a mutual recursive type).
An example of what the following means:
class Foo { Bar bar; } class Bar { Foo foo; }
To create something like this is currently impossible, but something that can be done (to some extent).
With some events, by the end of last year (2011) I allowed writing code in IronScheme, which works just as fast (or even faster) than in C #. The output of the IL code method exactly matches F # (by pure coincidence). I didnβt even bother to jump against IronPython / IronRuby. :)
Feel free to ask more if necessary.
In addition, there may be some informative discussions on the Codeplex bulletin board for IronScheme. I usually respond very quickly.
source share