Forum Discussion
I can only reply to n.4, with a sound "no".
Both languages execute on the same runtime and have basically the same underlying capabilities; the main difference is that VB.Net is not going to be updated further by Microsoft, so any language nicety that C# might get, from now on, will not necessarily have an equivalent in VB.Net.
It sounds like you're trying to figure out whether it makes sense to invest in C# or VB.Net for all rules. I think the answer has more to do with what you and your colleagues like the most. VB.Net is easier to read for non-programmers; C# is more rigid but less verbose and more featureful. Yes, technically you cannot write Member Formulas in C#, but you can place them in a shared BR, ticking the option "Contains Global Options For Formulas" and then call them with minimal scaffolding from the formulas:
Dim brObject as new OneStream.BusinessRule.Finance.MyRuleFile.MainClass()
brObject.MyFormulaForSomeAccount(si, globals, api, args)
So there is no real obstacle for C# hackers to write pretty much any code in OneStream. The real question is around maintainability - who will have to validate and maintain/tweak those rules, after the first development phase? Are they programmers at all? If these folks are not familiar with C# or programming in general, then VB.Net should be favoured.
Related Content
- 3 years ago
- 3 years ago
- 2 years ago
- 3 years ago