IronPython / IronRuby
IronPython in action will better explain this (and exactly how it is best to use IronPython), which can be placed in the SO response. I am biased - I was a technical reviewer and am a friend of one of the authors, but objectively I consider this a wonderful book. (I don't know if IronRuby would be blessed with such a wonderful book, though).
How do you want “one specific way for each answer” (incompatible with SO, which STRONGLY discourages a poster publishing 25 different answers if they have 25 “specific ways” to indicate ...! -): prototyping to learn which Either a specific assembly or collection that you are not familiar with (to check whether you understand their rights correctly and how to perform certain tasks) is much more productive in IronPython than in C #, since you can explore interactively and compile instantly and by necessary. (I have not tried IronRuby, but I assume that it can work about the same and fast).
source share