One other major reason is that VB supports optional parameters, and the Office object model made major use of optional parameters when it was created.

yag

>>I've wondered (again, just my opinion/speculation) if OLE Automation's roots in VBA means that VB.NET is better suited for it. I see more code samples for OLE Automation in VB.NET than C# (which could be for additional reasons).
>
>There is an article in the latest MSDN Magazine that seems to imply the same.
>
>Looks like I will have to install VB.NET as well as C# (:-()...
>
>Kevin