Need to start over on a project: vb or c#?

[Beemer Biker]

I have a C# project VS2005, that uses GridView and Multiview. It is
getting bigger then I originally anticipated and running slow and needs to
be broken up into several pages (yes, I am a newbie and made it one page)

It has been decided to use pintab instead of multiview. I downloaded pintab
and it has more vb examples than c#. It is not too late to start over in
VB if I wanted to. I googled around and found this discussion about which
was better
http://channel9.msdn.com/ShowPost.aspx?PostID=10894
but the members there were comparing VB6 to C# and I have Visual Studio 2005
with latest and greatest. I have found that c# seems to require more
casting than vb does especially when getting a control from a parent. VB
can pretty much enumerate the parent controls and intellisense list them
right away. C# also is multithreaded on forms whereas VB is not. That may
not apply to aspx as I have no separate tasks running mand dont plan to.

This is an in-house research app and needs to be done in a few weeks and I
am tempted to just stick with C# but I was wondering if anyone has a
different opinion.


--
======================================================================
Joseph "Beemer Biker" Stateson
http://TipsForTheComputingImpaired.com
http://ResearchRiders.org Ask about my 99'R1100RT
======================================================================

 

[clintonG]

Stick with C#. The rationale is simple. There are two tiers to web
development; server-side and client-side.
The client requires mastery of JavaScript and even more so now with AJAX and
with what is called Web 2.0 and mashups. JavaScript and C# syntax is exactly
alike and grammatically nearly so. Furthermore, so is Java. CSS syntax is
and all of these modern languages are all dervied from the legacy of C. So
you learn three or more languages for the price of one and have greater
opportunity to become masterful. It about being pragmatic.

For the most part noting I am still a neophtye to intermediate OOP developer
myself I believe you are mistaken about your presumption that C# requires
more casting than VB. Learning OOP is not intuitive and there is a lot of
code that is not as optimally written as it could be that has been put out
into the wild via blogs and so on. For example using early bound public
properties eliminates many circumstances that then require a cast for late
bound type identification.

You can also go through each page and disable ViewState for all uneeded
controls right in the declaration. That alone has helped some of my pages
get snappy. Have you learned to cache? That is another big deal many of us
haven't been using properly if at all.

Stick with C# Beemer and just learn to write better code...

 

[sloan]

//
I have found that c# seems to require more

casting than vb does especially when getting a control from a parent.

//


No , more likely VB.net does more "auto converting" for you than you
realize.
Option Explicit ON
Option Strict On

and you'll get the same behavior.

My opinion is that vb.net is deficient here, not better.


You might read this:
http://www.codeproject.com/dotnet/CSharpVersusVB.asp

 

[Steve C. Orr [MCSD, MVP, CSM, ASP Insider]]

You need to be careful. Asking a question like that is likely to start a
religious war!
I prefer VB.NET but I have nothing against C#.
The fact is they are virtually identical in every way that really counts.
So use whichever one you're more comfortable with.

 

[Jon Paal [MSMD]]

http://www.dnjonline.com/article.aspx?ID=mar05_vbvscsharp

http://www.skyscrapr.net/blogs/arcasts/archive/2006/10/10/341.aspx

 

[Rad [Visual C# MVP]]

I have a C# project VS2005, that uses GridView and Multiview. It is
getting bigger then I originally anticipated and running slow and needs to
be broken up into several pages (yes, I am a newbie and made it one page)

It has been decided to use pintab instead of multiview. I downloaded pintab
and it has more vb examples than c#. It is not too late to start over in
VB if I wanted to. I googled around and found this discussion about which
was better
http://channel9.msdn.com/ShowPost.aspx?PostID=10894
but the members there were comparing VB6 to C# and I have Visual Studio 2005
with latest and greatest. I have found that c# seems to require more
casting than vb does especially when getting a control from a parent. VB
can pretty much enumerate the parent controls and intellisense list them
right away. C# also is multithreaded on forms whereas VB is not. That may
not apply to aspx as I have no separate tasks running mand dont plan to.

This is an in-house research app and needs to be done in a few weeks and I
am tempted to just stick with C# but I was wondering if anyone has a
different opinion.

This thread is about to turn ugly! Before more heat is generated than noise
let me throw in my 2 cents.

If you know VB Classic or VB Script switch to VB.NET

If you know Java or C or C++ switch to C#

Functionally VB.NET and C# are about 99.9999999% alike in terms of the sort
of applications you can produce

 

[showhertheohface]

Big range of opinions on this subject. I've been using VB for 7 years
and C# for about 3. VB is much easier to learn but if you want to make
more money and have more projects available to you learn C#.

Erik Roessing