David, Is this your doing?
http://en.wiki.mcneel.com/default.aspx/McNeel/RhinoScriptingVsDotNet.html taz On Nov 7, 5:01 am, David Rutten <[EMAIL PROTECTED]> wrote: > Hi Oompa, > > There's an awful lot to say about this, but I'll keep it short. > VBScript has been around for ages and can be used to automate many > applications including Rhino, Excel, (Internet) Explorer..... > It's a scripting language with a very basic feature set. The syntax of > VBScript is derived from Visual Basic, but it is extremely forgiving. > > VB.NET syntax is also based on Visual Basic, but that's where the > overlap with VBScript comes to an end. VB.NET (like all languages that > work with the DotNET framework, such as C#, C++CLI, J#, IronPython, > IronDelphi etc. etc) is a fairly new arrival on the programming scene > and it's completely object oriented. Functions are no longer 'just > there' (like Sin() or Len(), but instead they are defined by certain > types (like the Math and String classes: Math.Sin() and > String.Length). > > VB.NET is (compared to VBScript): > - Faster > - More extensive > - More complicated > - Less forgiving > > It took me a while to switch from VBScript to VB6, and then again it > took me a few months to switch from VB6 to VB.NET and I'm still > learning new stuff almost every day (I've been doing this full time > for almost 4 years now). > > There is no step-by-step method to go from RhinoScript to Rhino > DotNET; functions have different names, different behaviour and a > different philosophy. > > -- > David Rutten > Robert McNeel & Associates > > ps. One last bit of bad news left: Grasshopper cannot run VBScript > code.
