Vista - Beginner - which is best dotnet.VB or dotnet.VC?

Hi All,

I have a number of databases which I would like to convert to VB or VC using
Microsoft Visual Studio Express. I know I cannot just click a button and
have everything done automatically and that I would need to learn to
program. What I would like to know is which language would be best for a
novice.

I've written a few bits of VBA and SQL but nothing spectacular, I have done
a little basic programming way back in the days of BBC and Commodore
Basic's.

So guys what would you suggest?

Thanks

Steve

Hi Steve,

I started programming in VB.net since I was already familiar with VB4/5 and
6, but the differences were so major that the several years of experience
with VB made little difference to me picking up VB.net.

After a short while programming in VB.net I started up a dotnet programming
hints and tips website, initially offering code examples in VB.net only.
However, after several requests for C# translations I decided to offer both
versions since I had bought Visual Studio and had both anyway. It took a
little while to get used to the syntax differences, but overall both
languages are pretty much the same and I picked up C# very quickly.

When first starting up, the main source of your knowledge is going to come
from code examples, and these are widely available in both VB and C# so that
isn't an issue.

I would suggest that you download and try them both out to see which you
prefer.

If you're not a touch typist, then it's probably a good idea to start with
VB as it's not case sensitive, and it will save you time in correcting if
you've not looked at the screen for a while. I regularly program in both
languages and can't think of any other reason to choose one over the other.
Even having thrown that in as an argument, I am not a touch typist but I
still use C# around 70% of the time. I just have a little curse every now
and then when I look at what I've just typed

--
Mick Doherty
http://dotnetrix.co.uk/nothing.htm

"SteveB" <steve@xxxxxx> wrote in message
news:EcSdnXyfw6CTVy_VnZ2dneKdnZydnZ2d@xxxxxx

Here is a subtle difference.

Google'ing for "how to's".

Since VB.NET is a later version (I use this term loosely) of VB, then when
you're looking for code samples, you will find google results from alot of
years, and alot of versions of VB code (as in, when you're looking, you'll
probably find VB.NET examples mixed in with VB6 (or 5 or 4 or before)
examples.

With C#, finding stuff via google is easier, since its relatively new. And
you only have to be careful to not do something in C# in a 1.1'ish way, that
there may be a 2.0 (or 3.0 or 3.5) way that is better.

Even when I'm coding in VB.NET (which is seldom these days), I still look
for answers via googling by typing in C# syntax?
Why? Because all the legacy vb examples don't come up to lead me down a red
herring link.

Subtle difference, but a difference.

...

Technically its just a preference of choice. So maybe you'll like typing
VB.NET code better.
I don't. I like the conciseness of C#.

Good luck with your decision.




"SteveB" <steve@xxxxxx> wrote in message
news:EcSdnXyfw6CTVy_VnZ2dneKdnZydnZ2d@xxxxxx

If you are looking to move into software development for a living, several large salary surveys I have seen indicated that C# developers make substantially more than VB.NET folks. In one survey the gap was around $18K/year.

To get VB.net results rather than VB classic in your google search results
just make .net a required term.

i.e. vb +.net database

--
Mick Doherty
http://dotnetrix.co.uk/nothing.htm

"sloan" <sloan@xxxxxx> wrote in message
news:#krkGluBJHA.3668@xxxxxx

You're right, that does cut down on the classic entanglement......

Maybe that google-tip .... and if vb.net 1.1 (or rather vb7? i can't
remember all the naming conventions) didn't have its deficiencies, I might
have stayed.
http://groups.google.com/group/micro...7b56f0b07cffcb

For the record, most have been addressed in 2.0. But those 1.1 years with
vb.net had some real gotchas.

............

Option JustLikeCsharp On
would be nice as well.

I have had several talks with junior developers about type safety. And when
we put it on (at the project/solution level in their vb.net projects), the
records is 212 errors. I was like "Hmm. Have a fun night fixing all of
those".

...







"Mick Doherty"
<EXCHANGE#WITH@xxxxxx[mick.doherty#dotnetrix.co.uk]>
wrote in message news:8F305B36-5339-4CCB-9A2C-568BDD410E57@xxxxxx

Microsoft defined VB as easy to use. Not just designed; it is defined to be
easy.

Microsoft could have made C++ easier to use, but declined to for some
reason. They seemed to have intentionally wanted it to be not as easy (you
fill in the explanation).

C# is somewhat the fulfillment of making C++ easier.

Without any further discussion, my impression is that VB .Net is the best
choice for you, and that is what you have chosen. Note however that
depending on what you need to do with the data, there might be other
alternatives. You might want to provide more details os what you need to do
and ask in a SQL Server group or forum or some other database group or
forum.


"SteveB" <steve@xxxxxx> wrote in message
news:EcSdnXyfw6CTVy_VnZ2dneKdnZydnZ2d@xxxxxx