How easy is it to learn VB compared to C#?

[Andy B]

How hard/easy is it to use/learn VB compared to c#?

[cfps.Christian]

Speaking as someone who knows both fairly well and has worked in both
a VB and C# environment I can say this. VB is generally easier to
learn, the syntax is fluid for someone that doesn't want to learn a
lot of technical terms. On the other hand C# isn't necessarily hard
to learn, but it's strictness forces you to write stronger code. In
all reality if you code VB without using the built in functions and
with Option Strict on you'll be able to move between the two rather
easily.

[Tom Shelton]

On 2008-05-29, rowe_newsgroups <ro********@yah oo.comwrote:

On May 29, 7:10 am, "Cor Ligthert [MVP]" <notmyfirstn... @planet.nl>
wrote:

>Andy,

Depends on what you want to learn

Programming: use C# as it is more strict with everything and does not
automaticly change your typing mistakes,

Learn to use a language to be productive: use VB as it does things that are
time spending to do with C# in many cases in a more easy way.

Just my opinion.

Cor

"Andy B" <a_bo...@sbcglo bal.netschreef in berichtnews:%2* *************** **@TK2MSFTNGP02 .phx.gbl...

How hard/easy is it to use/learn VB compared to c#?

I agree, C# is much more strict in the way it enforces rules. I would
say it would be very beneficial for new programmers to use C# and get
a hold on how things should work and prevent many "stupid" mistakes
(like implicitly returning value types and dumb casting errors).
However, once you have a firm grasp on how to program, I feel VB
(especially in VS 2008's IDE) makes it much, much easier to crank out
code. It just seems to flow better and is much more natural to write.

Thanks,

Seth Rowe [MVP]

I disagree. I think since vs2005, the C# editor is much more friendly.
Even the autoimplement stuff seems to be a little bit nicer in C#.

That's my opinion of course... The guy that LIKES case sensitivity.

--
Tom Shelton

[Patrice]

It's hard to tell as for example it depends on what you already know and as
personal preferences comes also in play...

IMO your best bet is just to start both and pick the one you prefer. The
more languages you know, the more asily you'll learn a new language (i..e.
on a logner term you may want to use one as your primary, nknow the second
enogh to be efficent plus perhaps JavaScript if you are doing web
development etc...)

--
Patrice

"Andy B" <a_*****@sbcglo bal.neta écrit dans le message de groupe de
discussion : ##************* *@TK2MSFTNGP02. phx.gbl...

How hard/easy is it to use/learn VB compared to c#?

[=?Utf-8?B?RmFtaWx5IFRyZWUgTWlrZQ==?=]

Frankly I like both. Some on our team pick VB, some pick c#. Those that
pick c# tend to have tasted java or c in their past. Maybe that makes an
easier migration. At least it should.

Out of curriosity, why didn't you crosspost to the c# group?
"Andy B" wrote:

How hard/easy is it to use/learn VB compared to c#?

[Rory Becker]

Hello Family,

Frankly I like both. Some on our team pick VB, some pick c#. Those
that pick c# tend to have tasted java or c in their past. Maybe that
makes an easier migration. At least it should.

If we could create MultiLanguage projects, then this problem would go away.

http://rorybecker.blogspot.com/2006/...ojects-in.html

The need to create a new project and therefore a new dll is massive overkill
just to be able to use the features of another language.

>
Out of curriosity, why didn't you crosspost to the c# group?

Probably didn't want to start a(nother) religious war :)
--
Rory

[Cor Ligthert[MVP]]

Tom,

That's my opinion of course... The guy that LIKES case sensitivity.

Have a look at VB, there it is automaticly set in the right case.

Kidding of course.

:-)

Cor

[=?Utf-8?B?RmFtaWx5IFRyZWUgTWlrZQ==?=]

That's an interesting concept in your blog. We've been happy
compartmentaliz ing our dlls fairly well (I hope...).

I wouldn't recommend taking too far though. I could imagine someone wanting
the next logical step, the following:

#region "Language=c #"
string message;
int index;
#end region

#region "Language=v b"
for index = 1 to 5 step 2
message = message & index.ToString( )
next
#end region

"Rory Becker" wrote:

Hello Family,

Frankly I like both. Some on our team pick VB, some pick c#. Those
that pick c# tend to have tasted java or c in their past. Maybe that
makes an easier migration. At least it should.

If we could create MultiLanguage projects, then this problem would go away.

http://rorybecker.blogspot.com/2006/...ojects-in.html

The need to create a new project and therefore a new dll is massive overkill
just to be able to use the features of another language.

Out of curriosity, why didn't you crosspost to the c# group?

Probably didn't want to start a(nother) religious war :)
--
Rory

[Tom Shelton]

On 2008-05-29, Rory Becker <ro********@new sgroup.nospamwr ote:

Hello Family,

>Frankly I like both. Some on our team pick VB, some pick c#. Those
that pick c# tend to have tasted java or c in their past. Maybe that
makes an easier migration. At least it should.

If we could create MultiLanguage projects, then this problem would go away.

http://rorybecker.blogspot.com/2006/...ojects-in.html

The need to create a new project and therefore a new dll is massive overkill
just to be able to use the features of another language.

>>
Out of curriosity, why didn't you crosspost to the c# group?

Probably didn't want to start a(nother) religious war :)
--
Rory

Rory,

I'm sure you know, it is technically possible to create multi-language
assemblies - there just is no support in the ide. You have to compile
from the command line to accomplish it.

The problem is that, I just don't really see the point of it. There
have been precious few times when I have wanted to mix languages, and
solution level support was more then adequate. The only time, that I
can really think of is using VB.NET for office automation, simply
because it is much easier and cleaner to use VB.NET for late-bound
scenarios - though, it looks as if that might change in C# v4.

I just don't see this as a feature that many developers will be
clamoring for.

--
Tom Shelton

[Andy B]

I am already somewhat experienced in C#. I have been using it for about 2 or
so years now and feel that I would have enough background to base a VB
comparison on. I haven't messed with VB though, and have no idea about its
learning curve. I didn't cross post either, because of reasons that I don't
think is right to say on a public list other than that whenever I post
there, I get harrassed with the idea that my posts and/or questions are too
vague and never do reach the point of "intellegen ce" or "accuracy". Guess
they are too lame to post overthere for some reason. Sorry for the short
lived vent, will get off my soap box now...
"Family Tree Mike" <Fa************ @discussions.mi crosoft.comwrot e in
message news:1B******** *************** ***********@mic rosoft.com...

Frankly I like both. Some on our team pick VB, some pick c#. Those that
pick c# tend to have tasted java or c in their past. Maybe that makes an
easier migration. At least it should.

Out of curriosity, why didn't you crosspost to the c# group?
"Andy B" wrote:

>How hard/easy is it to use/learn VB compared to c#?

[Rory Becker]

Hello Joergen,

I write mainly in VB.Net, but sometimes I just need to use
those darn unsafe pointers (for just a few functions) and
there is no substitute (that I know of) for those in VB.Net
so I have to create a separate project/dll and use ILMerge
in a post-compilation step if I do not want to distribute yet
another dll :(
/Joergen Bech

Annoying isn't it.

Someone correct me if I'm wrong....

Isn't XAML another language whose forms are compiled into the dll along with
C# Or VB.Net?

Surely XAML compilation isn't done by both CSC and VBC?

Isn't there a middle tier to the compilation already somewhere?

--
Rory