which One is Better

[Neetu]

Hi,
We are creating outlook Add-in using VSTO using Visual Studio 2008.
we are targeting for outlook 2003 and outlook 2007.

Before starting our implementation, We have to finalize on code of language.
We have got some feedback that it would be better to use Vb.net over c# .

Kindly suggest which language is best suited for add-in ( outlook and word)?
any Big Advantage of using vb.net over c#?

 

[Ken Slovak - [MVP - Outlook]]

Both are equally suitable, it's a matter of which language you are more
comfortable with. Code could even be written using both languages in the
same project, although I find that confusing myself.

 

[Neetu]

Thanks
Ken

Both are equally suitable, it's a matter of which language you are more
comfortable with. Code could even be written using both languages in the
same project, although I find that confusing myself.

 

[Baji]

You may have to look into this point also..

If you use VSTO, I see you need to create separate add-in for outlook
2003 & one more add-in for Outlook 2007.

 

[Neetu]

hello

I have got some inputs from some of people who worked on add-in project. and
there inputs are like


1. What language and development platform you use depends on what you're
most familiar with and most comfortable with.The choices also are influenced
by what versions of Outlook you're targeting, what versions of Windows,
whether or not the Framework will be installed already and what version, how
you intend to distribute the application and a number of other factors. For
example, for VSTO you would only be supporting Outlook 2003 Professional (not
standard or learning) or above and Outlook 2007. Depending on what version of
VSTO you might require Framework 2.0.Web services can be worked with natively
using a .NET language and from COM languages using the SOAP library.

2. C# has no support for optional parameters in method calls. However, the
objects that form the core partof the Office system are built on COM and
tuned for VBA code. These API’s expect optional parameters.Because of the
lack of support in C#, special place holders must be passed in for each call.
Using theseplaceholders for each method call can be tedious and demanding.
For instance, the document’s openmethod accepts 15 optional parameters.
Consider a Visual Basic example.

Me.CheckSpelling()

Now consider a C# example.

this.CheckSpelling(ref missing, ref missing, ref missing,ref missing, ref
missing, ref missing, ref missing, ref missing,ref missing, ref missing, ref
missing, ref missing);

The PIA’s that are installed during VSTO setup enforce a pass by reference
semantic on the caller for Microsoft Word development. For C#, the ref
keyword must be included to satisfy the requirement or a compilation error
will be generated. There is no workaround other than to add the ref keyword.
The arguments also must be variable references. Literals or strings cannot be
passed in because these do not satisfy the compiler requirement.

C# does not allow multiple arguments to properties. However, the Excel
object model supports such expressions. This is not a problem for Visual
Basic because the support has been continued for historic reasons.


Kindly give some feedback on it.