C# usage in COM heavy application

views:

answers:

+4 Q:

C# usage in COM heavy application

I would like to use C# for an application I'm building, but the application makes heavy use of automation (i.e. Excel, Word).

Is it feasible to use C# for such an application? It used to be a nightmare to use C type languages for things like parameter lists with null arguments etc..

What are some tips to make things easier or should I just stick with VB.NET?

Wait for C# 4, which supports optional parameters and implicit ref arguments.
It will make your life much easier.

Whether you use C# 4 or C# 3, you should use the Office Interop Extensions from the VSTO Power Tools; they will make your life even easier.

SLaks 2010-02-23 15:54:14

The typo makes this a bit unreadable. "Wait for C# for"?? I think you mean "C# foUr"

MarkJ 2010-02-24 09:53:56

@MarkJ: I can't believe I wrote that... Fixed; thanks.

SLaks 2010-02-24 13:59:10

+1 A:

It depends on what version of the language you're using. In .Net 4, C# supports named parameters (optional parameters). VB.Net has always had this. If you're not using .Net 4, I'd recommend using VB.Net for the interop bit - see this post from Scott Hanselman for an example.

Graham Clark 2010-02-23 15:57:59

This is a compiler feature. If you use the C# 4.0 compiler you can use optional parameters even in .Net 2.0 code.

Matthew Whited 2010-02-23 20:59:04

ansaurus

tags:

views:

answers:

C# usage in COM heavy application

related questions