Thanks for the reply. Are you aware of any technical reasons why we are limited to VB.Net?
Also why is it important for the business rule language to have similarity to the Excel macro language VB for applications? Much of our interaction with the API will use advanced programming concepts, like sessions and classes and interfaces and datasets. And the BR's can grow quite large. You mention macros, but I would only categorize a small number of our BR's as "macros".
I can understand why your underlying platform is built with C#. For exactly the same reasons you picked C#, some would rather pick C# for our custom extensions in OneStream.
I think I've heard that we can import our own assemblies, and use VB.Net as a simple shim. But it would be nice if C# was a first-class citizen of OneStream, just like VB. It doesn't sound like you had mentioned any technical reasons why OS is restricting customers to VB.Net, so it seems like the choice of a programming language should be left up to the customers.
Ideally VB should not be forced on us, especially if you aren't using it for the platform itself. Depending on the amount of customization, some customers may end up writing 10's or 100's of thousands of lines of code in OneStream, and ideally it wouldn't be a massive pile of VB code. I guess that last part is just my opinion.
