- Should I use a commercial component?
- Should I roll my own expression
evaluator? - Should I roll my own
dynamic language?
I know programmers are notorious for wanting to write their own language, but this is not the case here. The less work, the better. Lets assume that compatibility with Excel formulas is not a strict requirement; if there's a snappable component that uses formulas that aren't exactly the same as Excel formulas, that's fine.
Best Solution
Luca Bolognese has released a .NET library that provides the full set of financial functions from Excel. The main goal for the library is compatibility with Excel, by providing the same functions
http://blogs.msdn.com/lucabol/archive/2008/12/04/financial-functions-for-net-released.aspx