Maybe I really am a n00b

[ECathell]

Ok I have been programming in vb.net since it was released. I love it and I have a great time seeing my code come to life. Recently I have been seeking to expand my horizons(ie looking for a new job). I see a lot of C# jobs...C# this C# that. So I think to myself, ok ill start learning C#. So I start working on programs that I already have done in vb.net and working on transitioning them to C#.

I have come to the conclusion that intellisense in C# should be called dumbsense.
Property Creation is a pain.
Line terminators (Why are they needed?)
I couldnt get the class dropdowns to work like in vb.net....

Mostly I think C# is for those coders who like to bang their head against the wall....

CoderVB: So how was your day today? I got 3 different controls written and debugged.....
CoderC#: PAH! See this welt on my head? thats from the wall, see my cast on my arm? I got TCS from all the typing
CoderVB: Erm...ok Well what are you coding in?
CoderC#:<puffs out chest> I code in C#....
CoderVB:<to himself>hmm...B roken Head, Broken Wrist.....Nope Ill stick to my "inferior" vb.net.

--
--Eric Cathell, MCSA

[Cor Ligthert [MVP]]

Herfried,

I find the C# way more logical (I sometimes make mistakes in this)..
Moreover VBNet uses
Class MyOwnClass, what I find inconsequent.

I even don't see the need for Dim
"ds as dataset" tells that it is a declaration by the word "as".

However just a quick response not really something that bothers me or
something I have long thought about..

Cor

[Herfried K. Wagner [MVP]]

Cor,

"Cor Ligthert [MVP]" <no************ @planet.nl> schrieb:

I find the C# way more logical (I sometimes make mistakes in this)..
Moreover VBNet uses
Class MyOwnClass, what I find inconsequent.
I am not sure what you consider inconsequent here...
I even don't see the need for Dim
"ds as dataset" tells that it is a declaration by the word "as".

'Dim' is a keyword similar to 'Class', 'Function', and 'Sub'. You can
actually write 'Private Dim m_Foo As Integer', for example.

The problem with the C# solution for declaring local variables is that there
is no way for the IDE to determine if the user wants to start a variable
declaration. Note that in C++ local variable declarations can be preceeded
with 'auto', such as 'auto int foo', which would make support for meaningful
and valuable IntelliSense possible. C# does not even support the 'auto'
modifier for local variables.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[Cor Ligthert [MVP]]

>> Class MyOwnClass, what I find inconsequent.

I am not sure what you consider inconsequent here...
Dim ds as dataset
Dataset ds();
Class MyOwnClass
Class MyOwnClass

Makes this it clear?

I even don't see the need for Dim
"ds as dataset" tells that it is a declaration by the word "as".

'Dim' is a keyword similar to 'Class', 'Function', and 'Sub'. You can
actually write 'Private Dim m_Foo As Integer', for example.

As far as I can see it is there something double here, "dim" and "as" the
last tells as that it is a decleration.

In a function, Sub, or Class I cannot recognise it,
(it is the same as I always write about "then").

There can be in my opinion an option not to use it or an option to let
autocomplete automaticly add it.
The problem with the C# solution for declaring local variables is that
there is no way for the IDE to determine if the user wants to start a
variable declaration.

I don't see why that is a problem for *you*
:-))))))))))))

For others I agree with you, that you can see it as a disadvantage.

:-)

Cor

[Terry Olsen]

Back to the OP's OQ :) I've seen a lot of discussion here about the only
difference between C# and VB is the programmers preference in language. And
from what I've seen, It's not difficult to translate C# to VB. So maybe a
good VB programmer could convince those employers that his/her VB skills are
just as relavant for the job as the preferred C# skills. 6 in one,
half-dozen in the other...

[Bradley]

On Wed, 27 Jul 2005 07:08:45 -0600, "Terry Olsen"
<to******@hotma il.com> wrote:

Back to the OP's OQ :) I've seen a lot of discussion here about the only
difference between C# and VB is the programmers preference in language. And
from what I've seen, It's not difficult to translate C# to VB. So maybe a
good VB programmer could convince those employers that his/her VB skills are
just as relavant for the job as the preferred C# skills. 6 in one,
half-dozen in the other...

It takes any reasonable VB.Net programmer about a week to re-acclimate
and become just as productive in C# (and vice versa for C# coders).

Any hiring employer who balks over a week learning curve, or otherwise
refuses to hire a Dot Net developer because their experience is
limited to one language or another, is an idiot doomed for failure and
not worth working for anyway.

[ECathell]

So I shouldn't be intimidated by wanted adds that specifically ask for C#,
because I am capable of doing everything that they can do with VB.NET? I
just need to be able to explain that to them in a way they can grasp....

--
--Eric Cathell, MCSA
"Bradley" <pl****@nospam. com> wrote in message
news:dg******** *************** *********@4ax.c om...

On Wed, 27 Jul 2005 07:08:45 -0600, "Terry Olsen"
<to******@hotma il.com> wrote:

Back to the OP's OQ :) I've seen a lot of discussion here about the only
difference between C# and VB is the programmers preference in language.
And
from what I've seen, It's not difficult to translate C# to VB. So maybe a
good VB programmer could convince those employers that his/her VB skills
are
just as relavant for the job as the preferred C# skills. 6 in one,
half-dozen in the other...

It takes any reasonable VB.Net programmer about a week to re-acclimate
and become just as productive in C# (and vice versa for C# coders).

Any hiring employer who balks over a week learning curve, or otherwise
refuses to hire a Dot Net developer because their experience is
limited to one language or another, is an idiot doomed for failure and
not worth working for anyway.