C# and VB

I understand that :

VB only allows Managed and Safe code.
C# only allows Managed, Safe and Unsafe code.
VC++ allows Managed, Safe and Unsafe, and Unmanaged code.

They all will use the same IDE and forms builders, etc.
They all support the same OOP model under dotnet (1 inherited class, n+
interfaces).
It appears to be a preference of syntax - Verbal Bonus or Curt Shorthand.

Ralph Leckett

"Kevin Verble" <kevin.verble@greatplains.com> wrote in message
news:39c64695$1@news.dev-archive.com...
>
> Hello,
>
> I've read through the various articles and things on C#. I am unclear on
> when one might use C# versus VB. If they both use the CLR, then it would
> seem there would be no performance or memory issues to use to decide which
> one. Are there specific things that a C# program will be able to be used
> for that a VB program wouldn't ? Our company is considering switching
development
> environments from VB to C# for the creation of business objects. Is there
> some benefit that would out weigh the cost of retraining and the loss of
> the existing code base ?
>
> Thanks for any help or opinions.
>

My mistake.
How could I have possibly thought that anything that C++ produces was safe
:)

"Jeff Peil" <jpeil@bigfoot.com> wrote in message
news:39c67abe@news.dev-archive.com...
> Ralph,
>
> The MC++ compiler does not generate code that is verifiable as safe (in C#
> terminology, all methods produced with the MC++ compiler will be
considered
> as unsafe methods)
>
> "Ralph Leckett" <ralph@ils.net> wrote in message
> news:39c66140@news.dev-archive.com...
> > I understand that :
> >
> > VB only allows Managed and Safe code.
> > C# only allows Managed, Safe and Unsafe code.
> > VC++ allows Managed, Safe and Unsafe, and Unmanaged code.
> >
> > They all will use the same IDE and forms builders, etc.
> > They all support the same OOP model under dotnet (1 inherited class, n+
> > interfaces).
> > It appears to be a preference of syntax - Verbal Bonus or Curt
Shorthand.
> >
> > Ralph Leckett
>
>
>

I work for an eStrategy consulting firm that partners closely with Microsoft.
We have been programming .Net internally since the PDC and our Director
of Web Development spends a lot of time at Microsoft Headquarters "getting
the inside scoop".

Based on our conversations with Microsoft, our company's position is that
there is no significant advantage to one language over the other if all else
is equal because they are both fully-integrated with the CLR. VB programmers
would stick with VB, while C++ and Java programmers would go with C#. Functionally,
it still comes down to the CLR in the end.

"ralph" <nt_consulting32@hotmail.com> wrote in message
news:39c8c6dc$1@news.dev-archive.com...
>
> Whoa!
>
> Before we all go marching off the pier like Java-hyped lemmings - Stop and
> Think.
>
> Visual Basic (warts and all) and VC++ are established development
environments
> with almost 10 years of useage behind them. C# is a new proposal that will
> ship (maybe) sometime next year.
>
> It looks good and .NET makes sense but how stable is it going to be? Is it
> going to work out of the box? Where are the limitations? (You just know
"gotchas"
> are lurking out there somewhere.)
>
> Don't get me wrong. I plan on using C#, in fact I am using it, but I
suggest
> we let the wordsmiths, article writers, and others with time for
divertissements
> play with it for awhile before we bring it into a serious development
effort.
>
> Remember the old joke - "You can always tell a pioneer. He is the one with
> all the arrows stuck in his back."

The same thing would in this case apply just as much to VB.net. If you don't
think there is much new there, there isn't in C# either, as the two
languages share the same IDE, runtime environment and so on. C# is more an
interesting mix of earlier ideas than a whole new beast, IMHO.

This would not apply as much to VC++. True, many of the new features are
regarding CLR support and so on, but you can also continue working just as
you did before.

/Carl