For assembly, C# or VB or C++ ?

[Irene]

I am creating a project, which would have many assemblies in future.
The question is if I have a choice which language is better to create the
assemblies.
Or, there is no clear advantages one over another?

[Daniel O'Connell [C# MVP]]

"Irene" <Ir***@discussions.microsoft.com> wrote in message
news:15**********************************@microsof t.com...

I am creating a project, which would have many assemblies in future.
The question is if I have a choice which language is better to create the
assemblies.
Or, there is no clear advantages one over another?

You can mix and match them as you wish, to best suit whatever the assembly
does.

[Irene]

Are you implying that no language is better than others?
"Better" I mean that is "runs faster" or "make a smaller" or "easier to
design."

"Daniel O'Connell [C# MVP]" wrote:

"Irene" <Ir***@discussions.microsoft.com> wrote in message
news:15**********************************@microsof t.com...

I am creating a project, which would have many assemblies in future.
The question is if I have a choice which language is better to create the
assemblies.
Or, there is no clear advantages one over another?

You can mix and match them as you wish, to best suit whatever the assembly
does.

[Gerald Hernandez]

"Irene" <Ir***@discussions.microsoft.com> wrote in message
news:24**********************************@microsof t.com...

Are you implying that no language is better than others?
"Better" I mean that is "runs faster" or "make a smaller" or "easier to
design."

"Daniel O'Connell [C# MVP]" wrote:

In general, if you are writing managed code, then I would agree with that
implication.
Each language has some differences, but they all compile to pretty much the
same code.
For example, C# handles unsigned integers, while VB.Net does not.
But VB.Net handles late binding better than C#, and I find the IDE to be a
little more smooth.
In VS 2005, the current differences are further blurred making them even
more equal.
So it is more a matter of what are you most comfortable with and whether one
particular language has something in particular that you need that the other
does not.
Well written code in any of the languages will perform better than poorly
written code in another.
But all things being equal, when compiled they will all compile to the
almost the exact same code.

Gerald

[Daniel O'Connell [C# MVP]]

"Irene" <Ir***@discussions.microsoft.com> wrote in message
news:24**********************************@microsof t.com...

Are you implying that no language is better than others?
"Better" I mean that is "runs faster" or "make a smaller" or "easier to
design."

No one is better than the other in any general sense. In specific
circumstances, maybe, but not in general.

[Irene]

Thanks millions, Daniel and Gerald.
All things considered, I guess no language is superior to others.
I was assumed that C# was better for the managed code, because it probably
was designed for .NET.
"Gerald Hernandez" wrote:

"Irene" <Ir***@discussions.microsoft.com> wrote in message
news:24**********************************@microsof t.com...

Are you implying that no language is better than others?
"Better" I mean that is "runs faster" or "make a smaller" or "easier to
design."

"Daniel O'Connell [C# MVP]" wrote:

In general, if you are writing managed code, then I would agree with that
implication.
Each language has some differences, but they all compile to pretty much the
same code.
For example, C# handles unsigned integers, while VB.Net does not.
But VB.Net handles late binding better than C#, and I find the IDE to be a
little more smooth.
In VS 2005, the current differences are further blurred making them even
more equal.
So it is more a matter of what are you most comfortable with and whether one
particular language has something in particular that you need that the other
does not.
Well written code in any of the languages will perform better than poorly
written code in another.
But all things being equal, when compiled they will all compile to the
almost the exact same code.

Gerald

[Brooke]

I chose C# because the source code for the .NET platform is in C#. Makes it
easy to read the source and better understand what is going on behind the
scene.

Also, there are millions of lines of C and C++ code out there that can
easily be converted to C#. Especially handy when writing code for the
Compact Framework as it is missing many features that the desktop version of
..NET has and thus requires making API calls to get the desired
functionality.

"Daniel O'Connell [C# MVP]" <[e-mail]> wrote in
message news:OI**************@TK2MSFTNGP15.phx.gbl...

"Irene" <Ir***@discussions.microsoft.com> wrote in message
news:15**********************************@microsof t.com...

I am creating a project, which would have many assemblies in future.
The question is if I have a choice which language is better to create the
assemblies.
Or, there is no clear advantages one over another?

You can mix and match them as you wish, to best suit whatever the assembly
does.

[Brooke]

I guarantee that C# is just as easy (probably easier since you know C++)
as VB.NET. I have been using VB since it was first released and I was
actually a beta tester for "Thunder" when I lived in Seattle in the early
90's so I am very familiar with VB.

You cannot just jump from VB 6 to VB.NET, you have to take the time to
learn the new syntax, true OOP, and the .NET framework. Since you have to
"learn" VB.NET anyway, why not just make the jump right to C#?

To tell you the truth the two languages are almost exactly the same. If
you learn one you can pickup the other in just a few days. But like I said,
there are millions of lines of C and C++ that you can use in C#. If you have
to make an WIN API call it is very easy coming from a C/C++ background, but
it you are a VB programmer then it is not as easy.

To me there is really no good reason to learn VB.NET. I admit that I
have written and released VB.NET apps, but it was after I learned C#. There
are also more jobs here in Austin, Texas for C# programmers and for some
reason the wages are still higher (just like C++ over VB).

My theory is, "Stick to the three C's" (C, C++, and C#) and you should
always be able to find a decent job. Just about all operating systems can
run the C's apps and most of the embedded programming is done in the first
two "C's".

Bye

"Irene" <Ir***@discussions.microsoft.com> wrote in message
news:F3**********************************@microsof t.com...

Thank you, Brooke.
Your comments are very much convincing.
As a C++ programmer, I incline to C# too.
But, for its simplicity, I am kind of attracted to VB also.

"Brooke" wrote:

I chose C# because the source code for the .NET platform is in C#. Makes
it
easy to read the source and better understand what is going on behind the
scene.

Also, there are millions of lines of C and C++ code out there that can
easily be converted to C#. Especially handy when writing code for the
Compact Framework as it is missing many features that the desktop version
of
..NET has and thus requires making API calls to get the desired
functionality.

"Daniel O'Connell [C# MVP]" <[e-mail]> wrote in
message news:OI**************@TK2MSFTNGP15.phx.gbl...

>
> "Irene" <Ir***@discussions.microsoft.com> wrote in message
> news:15**********************************@microsof t.com...
>>I am creating a project, which would have many assemblies in future.
>> The question is if I have a choice which language is better to create
>> the
>> assemblies.
>> Or, there is no clear advantages one over another?
>
> You can mix and match them as you wish, to best suit whatever the
> assembly
> does.
>

[Irene]

Hi, Brooke:
This is actually a good news for me, since I've heard the same story (VB6
and VB.NET are miles different), and I feel more comfortable with learning C#.

3 C's... Hey, I want 3 A's.
That's just a Friday afternoon joke.

Once again, your comments are very much appreciated.
Good luck.
Irene.

"Brooke" wrote:

I guarantee that C# is just as easy (probably easier since you know C++)
as VB.NET. I have been using VB since it was first released and I was
actually a beta tester for "Thunder" when I lived in Seattle in the early
90's so I am very familiar with VB.

You cannot just jump from VB 6 to VB.NET, you have to take the time to
learn the new syntax, true OOP, and the .NET framework. Since you have to
"learn" VB.NET anyway, why not just make the jump right to C#?

To tell you the truth the two languages are almost exactly the same. If
you learn one you can pickup the other in just a few days. But like I said,
there are millions of lines of C and C++ that you can use in C#. If you have
to make an WIN API call it is very easy coming from a C/C++ background, but
it you are a VB programmer then it is not as easy.

To me there is really no good reason to learn VB.NET. I admit that I
have written and released VB.NET apps, but it was after I learned C#. There
are also more jobs here in Austin, Texas for C# programmers and for some
reason the wages are still higher (just like C++ over VB).

My theory is, "Stick to the three C's" (C, C++, and C#) and you should
always be able to find a decent job. Just about all operating systems can
run the C's apps and most of the embedded programming is done in the first
two "C's".

Bye

"Irene" <Ir***@discussions.microsoft.com> wrote in message
news:F3**********************************@microsof t.com...

Thank you, Brooke.
Your comments are very much convincing.
As a C++ programmer, I incline to C# too.
But, for its simplicity, I am kind of attracted to VB also.

"Brooke" wrote:

I chose C# because the source code for the .NET platform is in C#. Makes
it
easy to read the source and better understand what is going on behind the
scene.

Also, there are millions of lines of C and C++ code out there that can
easily be converted to C#. Especially handy when writing code for the
Compact Framework as it is missing many features that the desktop version
of
..NET has and thus requires making API calls to get the desired
functionality.

"Daniel O'Connell [C# MVP]" <[e-mail]> wrote in
message news:OI**************@TK2MSFTNGP15.phx.gbl...
>
> "Irene" <Ir***@discussions.microsoft.com> wrote in message
> news:15**********************************@microsof t.com...
>>I am creating a project, which would have many assemblies in future.
>> The question is if I have a choice which language is better to create
>> the
>> assemblies.
>> Or, there is no clear advantages one over another?
>
> You can mix and match them as you wish, to best suit whatever the
> assembly
> does.
>