Diff between VB.Net and C#.Net

[Rehan Mustafa Khan_MSFT]

Hi

Can anybody tell me what are the difference between VB.Net and C#

Thanks in advance

Rehan Mustafa Khan

[Jan Tielens]

The syntax is different.

:-) You can do the same with both of them, so based on functionality they
are more or less 100% the same.

--
Greetz,
Jan
__________________________________
Read my weblog: http://weblogs.asp.net/jan
"Rehan Mustafa Khan_MSFT" <v-******@online.microsoft.com> schreef in bericht
news:9A**********************************@microsof t.com...

Hi

Can anybody tell me what are the difference between VB.Net and C#

Thanks in advance

Rehan Mustafa Khan

[Armin Zingler]

"Rehan Mustafa Khan_MSFT" <v-******@online.microsoft.com> schrieb

Can anybody tell me what are the difference between VB.Net and C#

I am not sure whether this is a serious question - anyway, have a look at
nearly the same question in the thread "Benefits of VB.NET over C#", 13:19
your local time.
--
Armin

http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

[Herfried K. Wagner]

Rehan Mustafa Khan_MSFT schrieb:

Can anybody tell me what are the difference between VB.Net and C#

Interesting... You include "MSFT" in your name, are you a "Microsoftie"?

There are only little differences between C# and VB.NET, it's a choice
of personal preference. If you like the syntax of VB.NET more, use
VB.NET, if you are an ASCII art fan, then use C#.

--
Herfried K. Wagner
Microsoft MVP

[Cor]

Hi Rehan,

VB has more functions (methods)
C# has better posibilities for documentation (including intellisence)

For the rest the same if you make programs in VB.net with option strict on.

Cor

[Lorne Smith]

"Cor" <no*@non.com> wrote in message
news:#7**************@TK2MSFTNGP12.phx.gbl...

Hi Rehan,

VB has more functions (methods)
C# has better posibilities for documentation (including intellisence)

For the rest the same if you make programs in VB.net with option strict on.
Cor

Anyone who doesn't use Option Strict On needs a good spanking :) And is
likely to get one come compile time! :)

[Brian Henry]

looks like a msft person from the nntp posting heading... but as to why a
MSFT person couldn't find out the diffrences on their own web site is over
my head :P
"Herfried K. Wagner" <hi*******@m.activevb.de> wrote in message
news:3F**************@m.activevb.de...

Rehan Mustafa Khan_MSFT schrieb:

Can anybody tell me what are the difference between VB.Net and C#

Interesting... You include "MSFT" in your name, are you a "Microsoftie"?

There are only little differences between C# and VB.NET, it's a choice
of personal preference. If you like the syntax of VB.NET more, use
VB.NET, if you are an ASCII art fan, then use C#.

--
Herfried K. Wagner
Microsoft MVP

[Jay B. Harlow [MVP - Outlook]]

Lorne,

Anyone who doesn't use Option Strict On needs a good spanking :) And is
likely to get one come compile time! :) Actually, would this not be the other way around?

Option Strict Off will give you a runtime "spanking".

Option Strict On will give you a compile time "spanking".

As compile time "spankings" (aka errors) are almost always easier to "take"
(aka fix) then runtime "spankings".

Of course this may just be a "is the glass half full or half empty" thing
;-)

Hope this helps
Jay

"Lorne Smith" <[e-mail]> wrote in message
news:uH**************@TK2MSFTNGP10.phx.gbl...
"Cor" <no*@non.com> wrote in message
news:#7**************@TK2MSFTNGP12.phx.gbl...

Hi Rehan,

VB has more functions (methods)
C# has better posibilities for documentation (including intellisence)

For the rest the same if you make programs in VB.net with option strict

on.

Cor

Anyone who doesn't use Option Strict On needs a good spanking :) And is
likely to get one come compile time! :)

[Lorne Smith]

Weeelllll... I was *actually* referring to the spanking they'd get for not
using it to start with (literal spanking from collegues that is!!), followed
by the spanking they'd get for turning it on after the fact and realising
they've now go to do through 1000's of lines of code making sure their
variables are declared correctly! :)

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:OY**************@TK2MSFTNGP10.phx.gbl...

Lorne,

Anyone who doesn't use Option Strict On needs a good spanking :) And is likely to get one come compile time! :) Actually, would this not be the other way around?

Option Strict Off will give you a runtime "spanking".

Option Strict On will give you a compile time "spanking".

As compile time "spankings" (aka errors) are almost always easier to

"take" (aka fix) then runtime "spankings".

Of course this may just be a "is the glass half full or half empty" thing
;-)

Hope this helps
Jay

"Lorne Smith" <[e-mail]> wrote in message
news:uH**************@TK2MSFTNGP10.phx.gbl...

"Cor" <no*@non.com> wrote in message
news:#7**************@TK2MSFTNGP12.phx.gbl...

Hi Rehan,

VB has more functions (methods)
C# has better posibilities for documentation (including intellisence)

For the rest the same if you make programs in VB.net with option

strict on.

Cor

Anyone who doesn't use Option Strict On needs a good spanking :) And is likely to get one come compile time! :)