F# library expected to behave like C# when consumed

Question

I'm developing a library in F# for consumption by another team using C#. What things should I look out for knowing that this other team expects this library to behave like any other C# library?

For example if I use Options types I'll need to convert them to null when I expose to C#. Some other possible transition areas could be computation expressions, FastFunc, events and naming issues.

Answer 1

The F# Component Design Guidelines is a document designed to answer exactly this question.