Need to do simple windows programming with outlook integration do I use vba or c# ?

[Mrdzone]

Background:
80% web development 19% scripting 1% everything else.
Only windows programming background is a VB class i'm currently taking. At least I know how to do layouts and understand most windows concepts (handles to windows basic types for function calls etc...)

I don't want to use VB because if I'm going to go full blown app route I'd rather learn C# plus the very little VB i'm doing for this class makes me want to punch a baby.

App overview:

Currently a simple word document checklist

Features:
Link several outlook contacts to this document

When various boxes are checked either

1. add an outlook apppointment/send a meeting notice with the contacts linked earlier added as default recpients. The text of the appointment should be templated (ie initially propogated) but changeable.

2. Send an email (same templated but changeable format)

3. Schedule a todo (same format)


I assume if I go the c# route there is a library for outlook integration (hopefully free, possibly part of this .net thing i keep hearing about?) and I could just code up the various check boxes and associated text within the application.

But with the very very very little bit I know about VBA (mainly that it exists and is supposedly good for macroing office apps) it seems that this maybe easier.

Comments?

This message has been edited. Last edited by: Mrdzone, December 02, 2009 15:37

 

[Cogman]

Ok, VBA and VB are two different things. They use similar syntax, but they aren't the same thing.

Making a GUI in C#, from my experience, is pretty similar to that of VB. You are going to want to use some sort of GUI designer as programatically creating windows is a PITA.

As for the outlook integration, I'm not sure how easy it is. I've tried doing excel integration, and it isn't as easy as you might hope. (especially with c++, it may be easier with C# or VB, I haven't tried either).

I would say the learning curve for VB and C# is roughly the same, If you get a working solution in VB, then porting it over the C# shouldn't be too difficult. My advice is to use whatever you are comfortable with to do the project first, to ensure that you know how to do it, and then worry about learning a language.