VB for .NET Recommended?

[Guest]

Hi,

I'm considering using VB for .NET development (as opposed to C#). Does
anyone have advice?

Thank You

 

[Herfried K. Wagner [MVP]]

I'm considering using VB for .NET development (as opposed to C#). Does
anyone have advice?

I am wondering what you want to hear from people posting to a VB.NET group.
Personally I use VB.NET and C++(/CLI) when necessary and thus do not need
C#.

 

[VB Programmer]

I love VB.NET (hence my name).

I never use C# and dont need to for anything I do....

 

[Cyril Gupta]

It depends on what you are looking for. If you are looking for speedy
development go for VB. If you want slightly more power, spend more time
learning C#. I work with VB and I am pretty happy where I am.

Regards
Cyril Gupta

 

[Homer J Simpson]

I'm considering using VB for .NET development (as opposed to C#). Does
anyone have advice?

Not advice. VB will be faster to develop and cheaper to maintain. YMMV.

 

[Ken Tucker [MVP]]

Hi,

C# and VB.Net use the same framework. Why do you think that you
have slightly more power with C#?

Ken

 

[Cyril Gupta]

I think the power of a language goes deeper than what framework it is based
on. How the language is structured also does a lot for it. C# is a fully
object oriented language with advanced features like pointers. That's what
makes it slightly more powerful than VB. Of course you can nearly do in VB
what you can do in C#. But some things, like writing a directX game would be
more efficient done in c# then in VB.

Regards
Cyril Gupta

 

[_AnonCoward]

: Hi,
:
: I'm considering using VB for .NET development (as opposed to C#). Does
: anyone have advice?
:
: Thank You


Both VB and C# are comparable and can do pretty much the same things. The
differences are primarily in the syntax although the two languages bring
different advantages to the table (e.g.: C# supports 'unsafe' code whereas
VB doesn't).


Where do you plan on going with this and what is your background? If you
have no programming experience, you may find the more english like syntax of
VB easier to learn than C#. If you've coded in C/C++ or Java, you'd likely
be more comfortable with C#. It is often alleged that C# programmers are
more likely to demand a higher salary than VB.net programmers. That may be
true (I don't know, personally) and if so, reflects a market bias more than
anything else.


Examples are often given in C# on the web (although ASP.NET seems to have
more examples written in VB). That may be enough to sway you. In any event,
it wouldn't hurt to pick one language as your primary language for .net but
have at least a basic understanding of the other.

Ralf
--

 

[Guest]

Where do you plan on going with this and what is your background?

My background is C/C++/C# with some pre .NET VB experience. My interest/use
of .NET spans both web and desktop development.

I like to survery the landscape and hear pros and cons as part of my
decision processes. For example if someone could tell me hands down that VB
has a clear advantage for a particular task or area then I consider that
strongly.

The sense I get is that the whole point of .NET is that it is (supposed to
be) language neutral so that if one has a language preference they just use
that as there are no pressing factors. That being the case, and since I find
VB syntax/code format clearer than C-like languages (which I have used for
years) then I switching might be something to consider.

From the responses I've received, I see no pressing reason to switch (and
some potential reasons not to).

 

[Cor Ligthert [MVP]]

Cyril,

All your statements are wrong, except with the DirectX where you can use
unsafe code with C# are all statements wrong. The documentation around
DirectX beside C++ is by the way lousy for Net. For VB.Net there is almost
nothing while there is something for C#.

Using Net program languages is everything done by the CLI wherefore is
created intermediate code in the same way for all the languages.

Although there are some real Net parts which are basically not in C# however
standard alone in VB.Net which can make a VBNet program quicker than a C#
program. But you can import those almost all in C# as well.

Cor

 

[Cyril Gupta]

Hello Cor,

Hmm.... I am not contesting the CLI or the framework. I merely believe that
you can use pointers in C#, while in VB.Net you have to make do with
delegates, and that C# supports 100% object oriented features, while VB does
not. Are these statements wrong?

I need to re-study my books then

Heh
Cyril

 

[Cor Ligthert [MVP]]

Cyril,

All your statements are wrong,

In the previous message of course

)

Cor

 

[Cor Ligthert [MVP]]

Hello Cor,

Hmm.... I am not contesting the CLI or the framework. I merely believe
that you can use pointers in C#, while in VB.Net you have to make do with
delegates, and that C# supports 100% object oriented features, while VB
does not. Are these statements wrong?

I need to re-study my books then

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/csref/html/vcrefthedelegatetype.asp

VBNet supports 100% OOP. However does not do them the same as in the way as
it is done technical in C++. The last is in my opinion more and more a to
time consuming program-language to use for real standard business
applications.

Cor

 

[Armin Zingler]

Hi,

I'm considering using VB for .NET development (as opposed to C#).
Does anyone have advice?

Read the archives (groups.google.com). It's been discussed 1001 times.



Armin

 

[Ken Tucker [MVP]]

Hi,

Pointers are only supported by c# in unsafe code blocks.

Ken

 

[Herfried K. Wagner [MVP]]

I love VB.NET (hence my name).

I never use C# and dont need to for anything I do....

My experience with both VB.NET and C# is about 1:1, so I know C# and have
reasons not to recommend its use.

 

[Herfried K. Wagner [MVP]]

I think the power of a language goes deeper than what framework it is based
on. How the language is structured also does a lot for it. C# is a fully
object oriented language with advanced features like pointers.

VB.NET is an even more object oriented than C# is (built-in support for late
binding (polymorphism!), declarative interface implementation, ...) and
provides some great features like declarative event handling. For pointers
I prefer C++(/CLI) over C#. No need for C# at all.

That's what makes it slightly more powerful than VB.

This depends on how you define "power". I do not define it as some
nanoseconds faster execution, but instead a more powerful syntax.

what you can do in C#. But some things, like writing a directX game would
be more efficient done in c# then in VB.

Again I'd use C++ for this purpose.

 

[Herfried K. Wagner [MVP]]

Hmm.... I am not contesting the CLI or the framework. I merely believe
that you can use pointers in C#, while in VB.Net you have to make do with
delegates, and that C# supports 100% object oriented features, while VB
does not. Are these statements wrong?

The latter statement is wrong. VB.NET is more object oriented than C#. In
/addition/ it supports some non object oriented features which complement
the object oriented features perfectly. It's true that C# provides support
for pointers directly in the language, but there are only rare cases where
this feature is needed and thus I would not base my decision to use C#
instead of VB.NET on this little difference.

 

[_AnonCoward]

:
: "_AnonCoward" wrote:
:
: > Where do you plan on going with this and what is your background?
:
: My background is C/C++/C# with some pre .NET VB experience. My
: interest/use of .NET spans both web and desktop development.
:
: I like to survery the landscape and hear pros and cons as part of my
: decision processes. For example if someone could tell me hands down that
: VB has a clear advantage for a particular task or area then I consider
: that strongly.
:
: The sense I get is that the whole point of .NET is that it is (supposed to
: be) language neutral so that if one has a language preference they just
: use that as there are no pressing factors. That being the case, and since
: I find VB syntax/code format clearer than C-like languages (which I have
: used for years) then I switching might be something to consider.
:
: From the responses I've received, I see no pressing reason to switch (and
: some potential reasons not to).


Yeah, since you're familiar and comfortable with the C/C++ syntax already,
the move to C# will be very straight forward. Still, here is a URL you may
find useful (Top 10 reasons VB.NET is better than C#):

http://www.vbrad.com/pf.asp?p=source/src_top_10_vb.htm


And of course, there's this for the contrary view (Top 10 reasons C# is
better than VB.NET):

http://www.vbrad.com/source/src_top_10_cs.htm


I find it interesting that the C# listing is less substantial than the VB
list.


Ralf

 

[Cor Ligthert [MVP]]

Cyril,

Searching for something else my eye catched this article.

http://support.microsoft.com/default.aspx?scid=kb;en-us;308470

I thought just what we were talking about.

Cor