[dba-VB] C# vs VB - was RE: Renaming DBA-VB

The third is that it is what the customer wants.
Most of the contracting in the Houston, TX area
is for C# and not VB.net. No matter how you slice
this one, it comes up C#.

So, in the naming thing, DBA-DotNetLanguages is
probably too broad. Create 2 new ones (at least)
DBA-VBnet and DBA-C#. The the questions can fall
where they belong.



At 11:58 AM 10/23/2007, you wrote:
>Date: Tue, 23 Oct 2007 10:02:44 -0700
>From: Jim Lawrence <accessd at shaw.ca>
>Subject: Re: [dba-VB] C# vs VB - was RE:  Renaming DBA-VB
>To: dba-vb at databaseadvisors.com
>Message-ID:
>         <B19E9B532EE64BEBA7C7F34DDC9C3732 at creativesystemdesigns.com>
>Content-Type: text/plain; charset=us-ascii
>
>As far as I understand there are 2 possible reasons for going to C# if you
>are competent in VB.Net.
>
>1. The one key point for going to C# as apposed to Vb.Net would be for
>performance. That is not the case as they both perform equally so what is
>the advantage.
>
>2. The other point is that once an application is started in C# it has to be
>completed in C#. This is also not the case as .Net derivatives can be mixed
>and compiled.
>
>Jim