Re: Has MS given up on us (again)?
- From: "Alex Clark" <alex@xxxxxxxxxxxxx>
- Date: Wed, 13 Feb 2008 01:06:24 -0600
Hi Michael,
There's almost nothing to learn switching from VB to C#. You should have
it down pat in 1 day.
I can convert from C# to VB.NET relatively easily, but in order to do that I
tend to want to copy/paste and go through it line by line (unless it's some
ridiculously small example).
With MS putting examples for using their shiny new technologies in C#
exclusively, many of which don't have the most intuitive of syntax to begin
with, I'm then forced to do extra mental conversions which aren't always
easy if it's not immediately obvious as to what the code is doing (which is
often the case and is the whole reason I'm searching for examples to begin
with).
It would have been nice if MS had done the work of putting up VB code
alongside C# for all code samples in the documentation. Would have been
nice if they'd documented a lot of areas a bit more thoroughly as well
though, and actually provided sample code of *any* kind in many cases.
Our whole company switched from vb to c#. We had meeting and discussions
and more meetings and when we finally did it it was such a huge non-event
we all had a big laugh about it.
Just out of interest, what made your company want to make the change over to
C#?
.
- Follow-Ups:
- Re: Has MS given up on us (again)?
- From: cj
- Re: Has MS given up on us (again)?
- References:
- Has MS given up on us (again)?
- From: Alex Clark
- Re: Has MS given up on us (again)?
- From: Michael C
- Has MS given up on us (again)?
- Prev by Date: Re: Has MS given up on us (again)?
- Next by Date: Re: Printing
- Previous by thread: Re: Has MS given up on us (again)?
- Next by thread: Re: Has MS given up on us (again)?
- Index(es):
Relevant Pages
|
Loading