I use F # Interactive environment to write F # code most of the time. Even with Visual Studio, the F # Interactive environment does not (reasonably) support debugging, so I mainly rely on the ability to easily run something interactively and see if it works - if itβs not, itβs usually easy to break down into sub-components which can also be tried interactively. The great thing about F # Interactive, compared to, for example, GHCi, is that you can use it to evaluate almost anything - including type declarations.
The F # plugin for MonoDevelop 2.4 does not currently support debugging compiled F # applications. I was able to use the Mono debugger command line ( mdb , I think), but it was on a 32-bit system.
I'm not sure why MonoDevelop doesnβt select F # debugging symbols correctly, so this is most likely some basic error. There are several poeple working on the F # plugin for MD 2.6, so hopefully will be available soon. If someone wants to investigate why debugging doesn't work, that would be great ...
source share