🚀 go-pugleaf

The most confusing thing when using VB.Net and InDesign CS is the object browser doesn't agree with the documentation. Many objects show up as a generic Object when they should be a specific object. Then when you try to access functions or variables that are part of the specific object, Visual Studio only shows a choice of the function GetType. Then you have to ignore this and type in the function or variable you want and if you type it wrong there is no compiler error. Then when you run the program you get run time errors. As long as most errors end up as run time errors the advantage of compiling is gone. It is just as easy to write a scrip where all errors are run time errors anyway.

Furthermore VB.Net requires, as Ole says, several additional files to support the EXE. If they had a native mode where all the support libraries can be included in the EXE like C++ it would be a different story. All the marshaling of variables and just in time compiling has not made an improvement that I can see. Programs run very slow and there are more run time errors and fewer compile errors.

Ole is right, VBScripts are probably the way to go. Single stepping and examining variables is still available with the debugger.

Thanks
Jim