C# verses VB.Net Which Way to go. I am sure this issues has come up before.
Please direct me to any good articles that cover this issue. Ideally some
neutral assessment.

Its not likely there is a clear answer and you aren't going to find an
article that tells you which way to go in a neutral manner.However, I can
tell you this much, if you intend to do alot of interop with office or other
com applications, you will want to use VB.NET(optional parameters and better
latebinding), and if you are going to be operating over large buffers and
require alot of performance, C#(using unsafe code) will probably be the
better choice.
Most other things are a matter of personal preference.

"Robert Lario" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> C# verses VB.Net Which Way to go. I am sure this issues has come up
before.
> Please direct me to any good articles that cover this issue. Ideally some
> neutral assessment.
>
>

If you are totally a new guy to both of them, choose C#.
If you have a project to be done in days, and you are familiar with VB6,
then choose VB.Net.
Other wise, choose one by a coin.
"Robert Lario" <(E-Mail Removed)> дÈëÓʼþ
news:(E-Mail Removed)...
> C# verses VB.Net Which Way to go. I am sure this issues has come up
before.
> Please direct me to any good articles that cover this issue. Ideally some
> neutral assessment.
>
>

Hi Robert,

As Lario suggested, choosing between C# and VB.NET is mainly
a "lifestyle" choice. There have been heated debates in many
newsgroups, most often turning into flames :-). So ultimately it
depends on which language developers in your project are
comfortable with to adopt. For developers coming from a C++/Java
background, the natural choice is to adopt C#, whereas developers
from a VB backgroud are generally inclined to transition to VB.NET.

For an article on the syntactical comparison on the
differences between the 2 languages, please refer to the following link:
http://www.4guysfromrolla.com/webtech/012702-1.shtml

Regards,
Aravind C


"Robert Lario" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> C# verses VB.Net Which Way to go. I am sure this issues has come up
before.
> Please direct me to any good articles that cover this issue. Ideally some
> neutral assessment.
>
>

If you are used to VB-choose VB.NET
"Daniel O'Connell" <onyxkirx@--NOSPAM--comcast.net> wrote in message
news:#(E-Mail Removed)...
> Its not likely there is a clear answer and you aren't going to find an
> article that tells you which way to go in a neutral manner.However, I can
> tell you this much, if you intend to do alot of interop with office or
other
> com applications, you will want to use VB.NET(optional parameters and
better
> latebinding), and if you are going to be operating over large buffers and
> require alot of performance, C#(using unsafe code) will probably be the
> better choice.
> Most other things are a matter of personal preference.
>
> "Robert Lario" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > C# verses VB.Net Which Way to go. I am sure this issues has come up
> before.
> > Please direct me to any good articles that cover this issue. Ideally
some
> > neutral assessment.
> >
> >
>
>

"A.A. Fussy" <(E-Mail Removed)> wrote in message
news:%23L8Bq$(E-Mail Removed)...
> If you are used to VB-choose VB.NET

I don't consider that a good method to choose. Deciding on a language based
on what you used before instead of the task at hand is a foolish choice,
imho.

> "Daniel O'Connell" <onyxkirx@--NOSPAM--comcast.net> wrote in message
> news:#(E-Mail Removed)...
> > Its not likely there is a clear answer and you aren't going to find an
> > article that tells you which way to go in a neutral manner.However, I
can
> > tell you this much, if you intend to do alot of interop with office or
> other
> > com applications, you will want to use VB.NET(optional parameters and
> better
> > latebinding), and if you are going to be operating over large buffers
and
> > require alot of performance, C#(using unsafe code) will probably be the
> > better choice.
> > Most other things are a matter of personal preference.
> >
> > "Robert Lario" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > C# verses VB.Net Which Way to go. I am sure this issues has come up
> > before.
> > > Please direct me to any good articles that cover this issue. Ideally
> some
> > > neutral assessment.
> > >
> > >
> >
> >
>
>

For better market opportunities choose C#. This does not make much
difference to the project, but to you personally choosing C# will give you
better marketability.

I still do not understand why but the salary difference between a C#
programmer and a VB.NET programmer is as much as 20K. I think it might be to
do with the fact that...probably market is thinking that, normally C++/java
programmers (as many posts are suggesting) will migrate to C# and they have
better object oriented concepts. Is that why there is a salary difference of
about 20K? May be....


"A.A. Fussy" <(E-Mail Removed)> wrote in message
news:%23L8Bq$(E-Mail Removed)...
> If you are used to VB-choose VB.NET
> "Daniel O'Connell" <onyxkirx@--NOSPAM--comcast.net> wrote in message
> news:#(E-Mail Removed)...
> > Its not likely there is a clear answer and you aren't going to find an
> > article that tells you which way to go in a neutral manner.However, I
can
> > tell you this much, if you intend to do alot of interop with office or
> other
> > com applications, you will want to use VB.NET(optional parameters and
> better
> > latebinding), and if you are going to be operating over large buffers
and
> > require alot of performance, C#(using unsafe code) will probably be the
> > better choice.
> > Most other things are a matter of personal preference.
> >
> > "Robert Lario" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > C# verses VB.Net Which Way to go. I am sure this issues has come up
> > before.
> > > Please direct me to any good articles that cover this issue. Ideally
> some
> > > neutral assessment.
> > >
> > >
> >
> >
>
>

Hi Daniel,

In this context (between C# and VB.NET) what task is being solved by one
language than the other? They both are capable of solving the problem in
equal terms and the ultimate result is in IL right?


"Daniel O'Connell" <onyxkirx@--NOSPAM--comcast.net> wrote in message
news:(E-Mail Removed)...
>
> "A.A. Fussy" <(E-Mail Removed)> wrote in message
> news:%23L8Bq$(E-Mail Removed)...
> > If you are used to VB-choose VB.NET
>
> I don't consider that a good method to choose. Deciding on a language
based
> on what you used before instead of the task at hand is a foolish choice,
> imho.
>
> > "Daniel O'Connell" <onyxkirx@--NOSPAM--comcast.net> wrote in message
> > news:#(E-Mail Removed)...
> > > Its not likely there is a clear answer and you aren't going to find an
> > > article that tells you which way to go in a neutral manner.However, I
> can
> > > tell you this much, if you intend to do alot of interop with office or
> > other
> > > com applications, you will want to use VB.NET(optional parameters and
> > better
> > > latebinding), and if you are going to be operating over large buffers
> and
> > > require alot of performance, C#(using unsafe code) will probably be
the
> > > better choice.
> > > Most other things are a matter of personal preference.
> > >
> > > "Robert Lario" <(E-Mail Removed)> wrote in message
> > > news:(E-Mail Removed)...
> > > > C# verses VB.Net Which Way to go. I am sure this issues has come up
> > > before.
> > > > Please direct me to any good articles that cover this issue.
Ideally
> > some
> > > > neutral assessment.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

"Srinivas Kotipalli" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Daniel,
>
> In this context (between C# and VB.NET) what task is being solved by one
> language than the other? They both are capable of solving the problem in
> equal terms and the ultimate result is in IL right?
>

Both are possible, but each does provide a few small bits to help. As I
outlined in my first post, if you are dealing with alot of COM interop, VB
is invaluable with allowing you to use optional parameters and late binding,
instead of large amounts of empty values passed in which you are required to
in C#.
Same goes for image processing or large amounts of native interop, for
example. C#'s unsafe code facility allows you to more directly and simply
work with the data in a performant and efficent way.
If the project will not benifit from the particular facilities of either
language, then and only then should past comfort come into play, in that
case it doesn't matter what language you choose, just pick the one you want.
I can't tell you which you want, can I? .
If you are an old VB hand, I would actually recommend starting with C#(and
if you were an old C++ hand, perhaps VB would be better, but java probably
directly to C#) . It seems that people who start with a language different
from what they were used to pick up the .NET ideals and write more .NET like
code than if they go the direct update path. I see alot of C++ in C# code
being posted and people confused as to why it doesn't work, I can only
imagine that similar things happen with VB.

>
> "Daniel O'Connell" <onyxkirx@--NOSPAM--comcast.net> wrote in message
> news:(E-Mail Removed)...
> >
> > "A.A. Fussy" <(E-Mail Removed)> wrote in message
> > news:%23L8Bq$(E-Mail Removed)...
> > > If you are used to VB-choose VB.NET
> >
> > I don't consider that a good method to choose. Deciding on a language
> based
> > on what you used before instead of the task at hand is a foolish choice,
> > imho.
> >
> > > "Daniel O'Connell" <onyxkirx@--NOSPAM--comcast.net> wrote in message
> > > news:#(E-Mail Removed)...
> > > > Its not likely there is a clear answer and you aren't going to find
an
> > > > article that tells you which way to go in a neutral manner.However,
I
> > can
> > > > tell you this much, if you intend to do alot of interop with office
or
> > > other
> > > > com applications, you will want to use VB.NET(optional parameters
and
> > > better
> > > > latebinding), and if you are going to be operating over large
buffers
> > and
> > > > require alot of performance, C#(using unsafe code) will probably be
> the
> > > > better choice.
> > > > Most other things are a matter of personal preference.
> > > >
> > > > "Robert Lario" <(E-Mail Removed)> wrote in message
> > > > news:(E-Mail Removed)...
> > > > > C# verses VB.Net Which Way to go. I am sure this issues has come
up
> > > > before.
> > > > > Please direct me to any good articles that cover this issue.
> Ideally
> > > some
> > > > > neutral assessment.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Hi All,

Also, a comprehensive side-by-side syntax comparison.

http://www.harding.edu/USER/fmccown/...omparison.html

Regards,
Fergus

--
(Please ignore this - there's a feud going on)
==================================================
Quote of the day

Herfried:
I don't need/want human interaction.
==================================================