Hey, Einar,

I should probably qualify that it's a personal recommendation, though one based on some things I've encountered/observed over the last year.

I believe that OLE Automation is easier handled in VB.NET. It often requires more code in C#, and I've encountered some issues using C# for which I've never found a resolution (e.g. when spell-checking a document, I could never get the
collection of errors to populate in C#, though it does in VB.NET).

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).

I've also discovered some strange behavior using the newest Crystal COM object with C#, whereas things appear to be fine with VB.NET (though that's not relevant, because I decided to stick with the managed CR assemblies).

Perhaps there are answers and I just haven't discovered them - but even if I did, the beauty of .NET and the CLR is that I can write most of my assemblies in C# (which I strongly prefer), and use VB.NET for those few instances where I believe it's necessary.

Kevin