VB6 migration (C# or VB.NET?)

[=?Utf-8?B?Tm9ybWFuIExldmluc29u?=]

....from a purely technical/benchmarking standpoint looking 10-15 years out.
The concern being to best preclude/mitigate the situation currently facing
VB6 migration issues right now. Concern is not with training $, existing
developer knowledge, etc.

If we are given two choices which language to upgrade to, again, from a
purely technical/scalable perspective, is it more responsible to pursue C#
given it is a standard with both ISO and ECMA?

I would appreciate any input you can provide.

Thank you very much

[RobinS]

I already responded to this in the C# newsgroup. Here is my response.
Personally, I believe VB is easier, because it's more readable (to me) than
C#.
C# has more brevity.
-----

This question has been asked and answered a dozen times in the C# newsgroup
and in the VB newsgroup.

The languages are very similar, it's mostly a matter of taste. There are a
few things easier in one language than the other. For example, in VB, any
kind of Office programming is easier.

C# people think C# is better. VB people think VB is better.

If you're doing VB6, it will be a little bit less of a culture shock for
your programmers to migrate to VB.Net. (Been there, done that.)

Microsoft isn't going to drop the VB language if that's what you're worried
about. So I don't think it's "more responsible" to choose one over the
other in that regard.

If you want more info, search this newsgroup for "VB" and "C#".

Robin S.
Ts'i mahnu uterna ot twan ot geifur hingts uto.
---------------------------------------------------------
"Norman Levinson" <No************@discussions.microsoft.comwrote in
message news:F6**********************************@microsof t.com...

...from a purely technical/benchmarking standpoint looking 10-15 years
out.
The concern being to best preclude/mitigate the situation currently
facing
VB6 migration issues right now. Concern is not with training $, existing
developer knowledge, etc.

If we are given two choices which language to upgrade to, again, from a
purely technical/scalable perspective, is it more responsible to pursue
C#
given it is a standard with both ISO and ECMA?

I would appreciate any input you can provide.

Thank you very much

[Cor Ligthert [MVP]]

norman,

From your message I understand that your company in not using any MS Office
parts or other like that part because it is not ISO and not ECMA.

Or do I make a mistake?

Basic is a oldest Microsoft product that still exist.

Cor
"Norman Levinson" <No************@discussions.microsoft.comschreef in
bericht news:F6**********************************@microsof t.com...

...from a purely technical/benchmarking standpoint looking 10-15 years
out.
The concern being to best preclude/mitigate the situation currently facing
VB6 migration issues right now. Concern is not with training $, existing
developer knowledge, etc.

If we are given two choices which language to upgrade to, again, from a
purely technical/scalable perspective, is it more responsible to pursue C#
given it is a standard with both ISO and ECMA?

I would appreciate any input you can provide.

Thank you very much

[aaron.kempf]

VB is dead.

Steve Ballmer is a _C_FAG_ and doesn't understand the market. That is
the root of the problem.

VB has _ALWAYS_ been a better choice than C++ or C#.

WTF _IS_ C#? I don't think that I've ever heard of that programming
language; I sure don't see it in Visual Studio 6.

-Aaron

[aaron.kempf]

this DOTNET _CRAP_ doesn't work on Windows 2000, XP or Vista.

Vb6 works fine on all operating systems.

why leave vb6? It's better; it's faster.

FUCK DOTNET.

-Aaron

[BK]

You don't have to necessarily make a choice. We are a mixed language
shop. I have a team of 8 developers, 2 prefer C# and the rest prefer
VB. Since we design our apps for N-Tier, each developer has his/her
own area they are responsible for. The output of each programmers
work is an assembly (a DLL or Exe) that is consumed by other
programmers assemblies. The language doesn't really matter, once the
assembly is compiled a developer only needs to understand how to
consume it's services. That's the beauty of encapsulation.
Additionally, each programmer on the team is very comfortable looking
at someone else's code if necessary, even if that code is in the
language they don't prefer.

My preference is VB, to me it's more natural to read.

Hope this helps.

[aaron.kempf]

that is the stupidest thing I've ever heard

of _COURSE_ you should standardize on one language.
But MIcrosoft already killed off VB _ONCE_ do you trust them again?

Is VB 2002,2003,2005 _PRACTICAL_?

Is it either visual or basic?
Does it work on client machines?

>From where I'm standing this whole DOTNET thing is a scam and you

should stick with VB6.
like seriously here


On Feb 7, 5:38 am, "BK" <[e-mail]:

You don't have to necessarily make a choice. We are a mixed language
shop. I have a team of 8 developers, 2 prefer C# and the rest prefer
VB. Since we design our apps for N-Tier, each developer has his/her
own area they are responsible for. The output of each programmers
work is an assembly (a DLL or Exe) that is consumed by other
programmers assemblies. The language doesn't really matter, once the
assembly is compiled a developer only needs to understand how to
consume it's services. That's the beauty of encapsulation.
Additionally, each programmer on the team is very comfortable looking
at someone else's code if necessary, even if that code is in the
language they don't prefer.

My preference is VB, to me it's more natural to read.

Hope this helps.

[aaron.kempf]

seriously dude

where do you get off?

that's the stupidest idea I've ever heard of.

all I know is that this so called 'c-sharp' is about 4 times as
popular as anything VB crap microsoft has sold in the past 5 years.
so seriously-- I hae to say it but

VB IS DEAD
AND NO ONE CARES

IF THERE IS A HELL
SEND MICROSOFT THERE