For the last few years, I have been writing SW macros using VBA for work and they have really helped me in both getting my work done more quickly and in helping me apply drafting and modelling standards to a large number of files that have been created and edited by a long list of people. I am running into limitations of VBA that seem to not exist in C#. For example, some SYSTEM OPTIONS can be toggled using VBA commands. But, if there does not exist a VBA function to 'get' the status of an option, you won't know if your are enabling or disabling the command. Alternately, using C SHARP, one can read the registry and determine the status of an option before toggling it.
As I see it, I have to choose between C# and VB.NET to get around these limitations of VBA. I need help deciding between the two. What are the advantaged or disadvantages of those two options and are there any major characteristics that you feel heavily tilt the scale to either side.
Decades ago, I did a TON of programming in C and over the years have made several tools in Visual Basic and now VBA. I don't feel tremendously skilled in Object Oriented Programming, so one big factor for me will be if there is a good base of example code to draw from since I will be a beginner to either of those 'languages.