One of the first projects I tried on my own was to take a sample from MSDN that demonstrated menu operation. It was done with VB. The goal was to open a spreadsheet and load a new menu at that point that was applicable when a file was open in Excel (Print, Save, etc.).

I was surprised at the amount of work I had to do to convert to C#. Such as casting worksheets to workbooks, or vice versa, I don't remember which one C# doesn't understand. And casting cells to ranges.

It wasn't impossible. I just had to hunt down some requirements to get things to work in C#.

I would assume there's some public domain libs to make this more easier today.

>Hey, Craig,
>
>While I use C# for most things, VB.NET is much better suited for Word/Excel automation and integrating with COM.
>
>Now, VS2005 is supposed to have managed assemblies for Office automation, so that may make part of that point irrelevant...but for my 2003 projects, I always have at least one separate project for all my miscellaneous VB code to access COM components.
>
>Kevin