VB or C# for COM Interop?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

D P - 09 May 2006 02:17 GMT

Hi,

I'm a .NET beginner and I need to write a COM Interop for ASP 3.0. I don't
know which language is more advantageous for a COM Interop: VB or C#? I'm
reading documentation on both languages and I have a feeling that
implementing COM Interop in VB maybe easier. Please advise.

Thanks for your help.
DP.

Reply to this Message

The Real Andy - 09 May 2006 09:49 GMT

>Hi,
>
>I'm a .NET beginner and I need to write a COM Interop for ASP 3.0. I don't
>know which language is more advantageous for a COM Interop: VB or C#? I'm
>reading documentation on both languages and I have a feeling that
>implementing COM Interop in VB maybe easier. Please advise.

I assume you mean VB.net. At the end of the day as far as language is
concerned, it really makes no difference. Both languages achieve the
same result, the main difference being the syntax. In saying that, I
did hear at last years tech-ed that certain features such as generics
and iterators etc. might not be included in VB.net, but i have not
looked into this any further.

Furthermore, from what I have seen the industry seems to be adopting
C# as the 'got to have' language, so I would be inclined to use it
merely from a career point of view.

>Thanks for your help.
>DP.

Reply to this Message

D P - 10 May 2006 07:47 GMT

Very much appreciated. I prefer to write code in C# as well.
Thanks,
DP.

>>Hi,
>>
[quoted text clipped - 16 lines]
>>Thanks for your help.
>>DP.

Reply to this Message

yoga weazel - 10 May 2006 16:44 GMT

In addition, I have seen scenarios where, oddly enough, the equivalent VB.Net
and C# code executed at runtime differently! And it turned out the
unexpected behavior was in the VB.Net code. On the other hand I don't think
there are any C# specific "features" that VB.Net will not eventually have but
it just so happens that sometimes VB.Net gets those features later down the
road the C# does.

One of the selling points in my opinion is that (the following is typical
not absolute)

* VB programmers have a pretty big learning curve to pick up VB.Net
* Java programmers have a pretty small learning curve to pick up C#
* The learning curve for VB programmers to pick up C# is not any more
significant than picking up VB.Net (the biggest thing is to start thinking OO)

As a consultant I end up writing in whatever the client wants so I've done
both a pretty good bit. And from a career perspective (for the next several
years at least) there are A LOT! of companies out there that are starting to
worry about ongoing support for VB6 being dropped and are looking at
coversions/rewrites of their existing VB apps (I've done 3 in the last 2
years, 1 VB4 --> C# and 2 VB6 --> VB.Net). More times than not it's hard to
sell the guys who make the decisions that this conversion/rewrite is not any
more difficult in C# than VB.Net (e.g. educating them that VB is not VB.Net
and even the migration wizard in VS 2005 is kind of sketchy at times).

Just my 2cents (and then some:)

> >Hi,
> >
[quoted text clipped - 16 lines]
> >Thanks for your help.
> >DP.

Reply to this Message

The Real Andy - 11 May 2006 13:00 GMT

>In addition, I have seen scenarios where, oddly enough, the equivalent VB.Net
>and C# code executed at runtime differently! And it turned out the
[quoted text clipped - 20 lines]
>more difficult in C# than VB.Net (e.g. educating them that VB is not VB.Net
>and even the migration wizard in VS 2005 is kind of sketchy at times).

You make a good point. The company i currently work for hired a VB
programmer to work on a VB.net project. He lasted about 2 months, left
never understanding OO. The sad part was that the manager who hired
him thought vb was the same as vb.net. Even worse, the PB programmers
picked up VB.net before he could, but that is just one person.

I am from an embedded backround (asm and c) and now write c++. I am
finding it difficult to transition from c++ to c#. Yet in saying that
I can move from vb.net to c# with no problems at all. However, being a
c++ programmer i much prefer the c# syntax, as it makes more sense to
me. C# is good, i just fail to understand a few concepts, and i really
miss pointers :)

In saying all that, the current trend here in AU seems to be
converting everything to c#. Everyone seems to want c# programmers
with either vb experience or c++ experience, depending on the project.

Andy

Reply to this Message

VB or C# for COM Interop?

Free Magazines