09-19-2023 07:52 AM
We are still in the development stage of our OneStream implementation. We are currently running 7.4. When v8.0 came out, I started doing some research on .NET6 (and 7). It appears that Microsoft is more focused on CSharp than they are on Visual Basic. I believe, eventually, Visual Basic will be deprecated. With this in mind, and since we are still in development, I was thinking about converting our VB business rules to CSharp and using that language going forward.
I would like the feedback of the OneStream Community before I take this project on.
Thank you.
09-19-2023 02:36 PM
At this point, my opinion is that this decision is purely customer driven as they will be responsible for maintaining the rules and member formulas post go-live. I would guess that there are currently far more OneStream consultants with VB.net experience than C# experience so that may be a factor in your decision, but I also know that free online converters could help in those situations.
The deprecation of VB.net may or may not happen and when/if it does, will it be in three, five, ten years? We went through the deprecation of Silverlight in 2021 and we successfully navigated that change with our customers.
09-21-2023 05:00 AM - edited 09-21-2023 05:05 AM
As @chul said, there isn't a single answer. I would add that