[AccessD]OT: C# was no-ip.com

Marcus, Scott (GEAE, Contractor) scott.marcus at ae.ge.com
Mon Jul 28 11:02:42 CDT 2003


John,

You must have read the same article as me (actually editors comments). I'm
leaning VB.Net first and then adding C# to my skills. Seems silly to me that
C# pulls in more money. Like you, that is why I'm going to learn it also.
Have you seen any silly job postings like "C# developer with 5 years
experience..."?

Have you found that your Access framework already has equivalents in .Net
framework?

I'm not far enough into .Net to have an opinion yet. I can say that if it is
similar to how Java works, I won't like it. I hear that C# is very close to
Java.

What I've learned in VB.Net so far seems pretty straight forward.

My only doubts about .Net is that I'm not seeing very many job postings for
.Net developers (but allot more than Access development).

Scott

-----Original Message-----
From: jcolby at colbyconsulting.com [mailto:jcolby at colbyconsulting.com]
Sent: Monday, July 28, 2003 11:47 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD]OT: C# was no-ip.com


Scott,

Not yet, though I think I will end up there.  I'm thinking that learning
VB.Net and more importantly the .net framework FIRST will be most useful to
me.  The framework is massive and being comfortable with that is a
requirement regardless of the language you then use for your programming.

Once that is done I will probably move to C# for the simple reason that the
polls indicate C# programmers get better money.  I did a controller project
down in Mexico in a custom 'C' language so it isn't totally foreign.

Again though, the whole point of the .Net concept is that the framework
really provides about 90% of the functionality and it is used EXACTLY the
same regardless of the language you use.  The language itself is really a
thin veneer over the top of the framework.  Even things like variables are
framework objects so that any .net language can literally pass their
variables back and forth without the silly problems like you see with VB and
C not treating strings the same way.

John W. Colby
www.colbyconsulting.com



More information about the AccessD mailing list