Why bother with .Net language conversion?

[Jim Lincoln]

There are various utilities that you can buy to convert VB.Net to C#
(C-Sharpener For Vb, Instant C#, etc.). I'm sure there are others that
convert C# to VB.Net. I don't understand the point of these tools. MS
designed .Net so that I can create assemblies in one language (VB for
instance) and call the assembly from a different language (C# for
instance).

Why bother to convert code from one language to another then? Are some
of you on projects that require everything to be in either C# or
VB.Net? Aren't the languages pretty much the same, so that it is easy
to move between the two?

Thanks for any insight.

Jim Lincoln

[Marina]

Yes, the languages are very similar. However, certain companies feel more
comfortable having their entire team work in one or the other, depending on
what the company was using before. If they were using VB6, their developers
will feel more comfortable with VB.NET because of the familiar syntax. The
entire project will then be in VB.NET, so that whenever anyone has to go
modify anyone else's code, the syntax will be familiar and consistent.

"Jim Lincoln" <so*******@yahoo.com> wrote in message
news:21**************************@posting.google.c om...

There are various utilities that you can buy to convert VB.Net to C#
(C-Sharpener For Vb, Instant C#, etc.). I'm sure there are others that
convert C# to VB.Net. I don't understand the point of these tools. MS
designed .Net so that I can create assemblies in one language (VB for
instance) and call the assembly from a different language (C# for
instance).

Why bother to convert code from one language to another then? Are some
of you on projects that require everything to be in either C# or
VB.Net? Aren't the languages pretty much the same, so that it is easy
to move between the two?

Thanks for any insight.

Jim Lincoln

[Mark Broadbent]

....and lets face it, who the hell likes vb code urrrgh! :)

--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"Marina" <so*****@nospam.com> wrote in message
news:u4**************@TK2MSFTNGP12.phx.gbl...

Yes, the languages are very similar. However, certain companies feel more
comfortable having their entire team work in one or the other, depending on what the company was using before. If they were using VB6, their developers will feel more comfortable with VB.NET because of the familiar syntax. The entire project will then be in VB.NET, so that whenever anyone has to go
modify anyone else's code, the syntax will be familiar and consistent.

"Jim Lincoln" <so*******@yahoo.com> wrote in message
news:21**************************@posting.google.c om...

There are various utilities that you can buy to convert VB.Net to C#
(C-Sharpener For Vb, Instant C#, etc.). I'm sure there are others that
convert C# to VB.Net. I don't understand the point of these tools. MS
designed .Net so that I can create assemblies in one language (VB for
instance) and call the assembly from a different language (C# for
instance).

Why bother to convert code from one language to another then? Are some
of you on projects that require everything to be in either C# or
VB.Net? Aren't the languages pretty much the same, so that it is easy
to move between the two?

Thanks for any insight.

Jim Lincoln

[Cowboy \(Gregory A. Beamer\) [MVP]]

It is wise to have an entire team on the same language for cost reasons.
Mixed languages mean you have to train your guys for all languages employed.
That can get expensive.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************
"Jim Lincoln" <so*******@yahoo.com> wrote in message
news:21**************************@posting.google.c om...

There are various utilities that you can buy to convert VB.Net to C#
(C-Sharpener For Vb, Instant C#, etc.). I'm sure there are others that
convert C# to VB.Net. I don't understand the point of these tools. MS
designed .Net so that I can create assemblies in one language (VB for
instance) and call the assembly from a different language (C# for
instance).

Why bother to convert code from one language to another then? Are some
of you on projects that require everything to be in either C# or
VB.Net? Aren't the languages pretty much the same, so that it is easy
to move between the two?

Thanks for any insight.

Jim Lincoln

[Mark Broadbent]

LOL! Ive not laughed so much in ages! cheers Owyn. Just kidding around
though -I come from a VB background and I think it sometimes shows by all my
stupid questions to this newsgroup.

I do definately prefer C# but Im also the first to critise if I think it
should do something that is easy in VB (e.g. ranges in case statements).

By the way your dog is definately bigger than mine, I only have cats (that
probably confirms Im a snob!).

Thanks again. i needed cheering up.
bye for now.
--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"owyn" <ow**@discussions.microsoft.com> wrote in message
news:D1**********************************@microsof t.com...

Me. I have to use both VB and C# and most of the difference is personal choice. C# is the snob favorite mostly because it has the {} thing that
seems to spell "Look how smart I am." Then the C# camp sells management on
the language and the world has to keep up with the curly braces. In the end
if I needed to do something I could get it done in either language, but not
always the same way. If there was a difference in performance it was some
where out in the microsecond area. This is why people end up in wars. Just
because someone says, "My dog is bigger than your dog."

"Mark Broadbent" wrote:

....and lets face it, who the hell likes vb code urrrgh! :)

--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"Marina" <so*****@nospam.com> wrote in message
news:u4**************@TK2MSFTNGP12.phx.gbl...

Yes, the languages are very similar. However, certain companies feel more comfortable having their entire team work in one or the other, depending

on

what the company was using before. If they were using VB6, their

developers

will feel more comfortable with VB.NET because of the familiar syntax.

The

entire project will then be in VB.NET, so that whenever anyone has to

go modify anyone else's code, the syntax will be familiar and consistent.

"Jim Lincoln" <so*******@yahoo.com> wrote in message
news:21**************************@posting.google.c om...
> There are various utilities that you can buy to convert VB.Net to C#
> (C-Sharpener For Vb, Instant C#, etc.). I'm sure there are others that > convert C# to VB.Net. I don't understand the point of these tools. MS > designed .Net so that I can create assemblies in one language (VB for > instance) and call the assembly from a different language (C# for
> instance).
>
> Why bother to convert code from one language to another then? Are some > of you on projects that require everything to be in either C# or
> VB.Net? Aren't the languages pretty much the same, so that it is easy > to move between the two?
>
> Thanks for any insight.
>
> Jim Lincoln

[Mark Rae]

"Mark Broadbent" <no************@no-spam-please.com> wrote in message
news:es**************@TK2MSFTNGP10.phx.gbl...

By the way your dog is definately bigger than mine, I only have cats (that
probably confirms Im a snob!).

This must be a cue for someone to do a pussy joke... :-)

[Mark Broadbent]

Ya got there first!

--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"Mark Rae" <ma**@mark-N-O-S-P-A-M-rae.co.uk> wrote in message
news:u6**************@TK2MSFTNGP11.phx.gbl...

"Mark Broadbent" <no************@no-spam-please.com> wrote in message
news:es**************@TK2MSFTNGP10.phx.gbl...

By the way your dog is definately bigger than mine, I only have cats (that probably confirms Im a snob!).

This must be a cue for someone to do a pussy joke... :-)