"Srinivas Kotipalli" <srinivask@sbcglobal.net> wrote in message
news:OSheOKppDHA.2188@TK2MSFTNGP11.phx.gbl...[color=blue]
> 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?
>[/color]
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.
[color=blue]
>
> "Daniel O'Connell" <onyxkirx@--NOSPAM--comcast.net> wrote in message
> news:eXpAYEppDHA.3504@TK2MSFTNGP11.phx.gbl...[color=green]
> >
> > "A.A. Fussy" <amarks@austarnet.com.au> wrote in message
> > news:%23L8Bq$opDHA.2188@TK2MSFTNGP11.phx.gbl...[color=darkred]
> > > If you are used to VB-choose VB.NET[/color]
> >
> > I don't consider that a good method to choose. Deciding on a language[/color]
> based[color=green]
> > on what you used before instead of the task at hand is a foolish choice,
> > imho.
> >[color=darkred]
> > > "Daniel O'Connell" <onyxkirx@--NOSPAM--comcast.net> wrote in message
> > > news:#Y5n2VopDHA.3844@tk2msftngp13.phx.gbl...
> > > > Its not likely there is a clear answer and you aren't going to find[/color][/color][/color]
an[color=blue][color=green][color=darkred]
> > > > article that tells you which way to go in a neutral manner.However,[/color][/color][/color]
I[color=blue][color=green]
> > can[color=darkred]
> > > > tell you this much, if you intend to do alot of interop with office[/color][/color][/color]
or[color=blue][color=green][color=darkred]
> > > other
> > > > com applications, you will want to use VB.NET(optional parameters[/color][/color][/color]
and[color=blue][color=green][color=darkred]
> > > better
> > > > latebinding), and if you are going to be operating over large[/color][/color][/color]
buffers[color=blue][color=green]
> > and[color=darkred]
> > > > require alot of performance, C#(using unsafe code) will probably be[/color][/color]
> the[color=green][color=darkred]
> > > > better choice.
> > > > Most other things are a matter of personal preference.
> > > >
> > > > "Robert Lario" <lario@nospam.inherit.com> wrote in message
> > > > news:uxnbbRopDHA.1408@TK2MSFTNGP11.phx.gbl...
> > > > > C# verses VB.Net Which Way to go. I am sure this issues has come[/color][/color][/color]
up[color=blue][color=green][color=darkred]
> > > > before.
> > > > > Please direct me to any good articles that cover this issue.[/color][/color]
> Ideally[color=green][color=darkred]
> > > some
> > > > > neutral assessment.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]
