I have read lots of favorable things about programming with MS .net,
and I am curious for opinions on why VB .net vs C# net.
Simply language choice ?

Programming is frequently about right tool for right job.
When pdox isnt the right tool, I believe I need to round out my tool set.
Others have mentioned java, and while that has merits,
I think my personal background with turbo C and c++ would
be better leveraged in c# net.
I also have some experience with visual basic.

Is VB net easier to learn ?
More widely accepted ?

All thoughts, comments, and experiences are welcome.


Robert Wiltshire

With the current versions of VB.net and C#, feature sets are at parity -
you can pretty much do anything in one that you can do in the other.
There are probably a few things that "fit" one or the other better, but
I can't really give you any examples.

Microsoft's recommendation is that if you have a background in C, C++,
Java, or don't have a background in VB or other BASICs, go with C#. If
you have a background in VB or another BASIC, MS recommends you go with
VB.net.

Compiled code written in either can be accessed by the other.

Looking at open source and posted code on the web, it seems to me that
more of the interesting and/or complex examples are done in C#, while
more beginner's stuff is in VB.net. On MSDN, most topics have examples
in both, with only slightly fewer having examples in J++.

As far as which is easier to learn, if you're comfortable with C, C++,
or Java syntax, there's probably not much difference; VB.net (like most
flavors of BASIC) is pretty verbose, whereas C# requires ending lines
with semi-colons, designating blocks of code with braces, and is much
terser, so for folks with no programming experience, VB.net probably is
probably easier to get started with.

The code completion and Intellisense support in Visual Studio is a lot
more complete for VB.net in Visual Studio 2003; supposedly, the gap is
closed quite a bit in Visual Studio 2005, withe Intellisense for C#
almost as complete as it is for VB.net.

Regardless of which language you make your primary coding language, it's
worthwhile to learn enough about the other to be comfortable reading it
so that you can make use of examples provided in either language.
Although there are translation tools that go both ways, that's a lot of
trouble to go to just to be able to understand an example.

For an alternative to Visual Studio, check out Sharp Developer
(http://www.icsharpcode.net/OpenSource/SD/). It's an open source C# IDE.

Robert wrote:

Robert wrote:

C => C++ => Java => J++ => C#

I think your C/C++ background will serve you well in either Java or C#, but
I also think you could probably move back and forth between the two.

In any event, C# is very very similar to Java, from what I've seen.

--
Larry DiGiovanni
Digico, Inc.
IT Consulting and Staffing Solutions
www.digicoinc.com
Check out www.thedbcommunity.com for Paradox resources.

Hi!


Where do you put J# ?



@-salutations

MCI

Hi!

Please, considere IronPython
http://www.codeplex.com/Wiki/View.as...ame=IronPython



@-salutations

MCI

Méta-MCI wrote:

Was there a J#? I have no idea. I am basing the below geneology on dim
recollection and the fact that C# code I've seen looks very much like Java
code, down to the packages, etc.

--
Larry DiGiovanni
Digico, Inc.
IT Consulting and Staffing Solutions
www.digicoinc.com
Check out www.thedbcommunity.com for Paradox resources.

Robert wrote:
I think that the whole concept behind "dot-net" is to provide a
language-independent high-level environment .. in which you can use
the "tool de jour" and wind up with an equally-acceptable result.

Pick your language .. what comes out the back-end of the compiler is a
bytecode pseudo-executable that works the same way as any other. Instead
of relying upon a language-dependent runtime (e.g. MSVCRTxx.DLL), the
runtime support is provided by the framework (i.e. "Windows") itself.

An ambitious but noble goal, and if I must say, they did rather a fine job
of it. :-)

----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com

Interesting read

http://www.codeproject.com/dotnet/CSharpVersusVB.asp

I remember when Turbo Pascal was released for $150 at the time that MS
Pascal was more than $1,000. It was cheaper to buy Turbo Pascal than to
photocopy the MS Pascal manual.

I also bought a betacord video player ("the $200 digital clock") and an
Amiga.

Nothing will stop VB.net....

"Robert" <nomail (AT) nospam (DOT) com> wrote