Disclaimer: I have never worked with Perl or Python.
If you are ready to “activate” macros and VBA with Visual Studio Office Tools (VSTO), which have been available in .NET for some time, you have several powerful new features for interacting with Interop:
Using the COM API, as shown through the PIA (Primary Interop Assemblies) used in C # and other .NET languages: the many code examples available here in SO or CodeProject to do all the things you describe. We suggest that you search for "C # Office Interop" "C # Outlook Interop" "C # Excel Interop" "C # Office Automation". Or search in other .NET languages from VB.NET to F #.
With the latest .NET tools, you have custom designers that let you create add-ins for Excel or Outlook, etc. I'm working on an Excel add-in in 2010 right now, and it's pretty nice to be able to drag and drop WinForms controls onto WorkSheet and create event handlers and edit properties during development in the same way as in WinForms. Of course, the 2010 beta has some rough edges, as you might expect.
VSTO Forum on Microsoft: VSTO Forum for Office 2003, 2007
A good "portal" for automating Office through VSTO: Getting Started (Visual Studio Tools for Office)
VSTO Forum at Microsoft Beta for Visual Studio 2010 2: 2010 Beta Be sure to open the drop-down panel under the heading "Ads" "Office Development with Visual Studio 2010 Beta Resources"
Microsoft Office 2010 Beta: Office 2010
In the beta version of Visual Studio 2010 2, using the beta version of Office 2010, you have at least six types of projects related to interacting with Excel:
Excel 2007 Add-in, Excel 2010 Add-in, Excel 2007 Template, Excel 2010 Template, Excel 2007 Workbook, Excel 2010: For Outlook: Outlook 2007 Add-in, Outlook 2010 Add-in
This SO Stream Starts VSTO? may have some meaning for you, and I suggest you do a search here on SO on "VSTO Excel" and "VSTO Outlook"
Billw source share