|
WOW... there is no difference between...
dim MyVariable as Integer
and
Integer MyVariable;
??? I think the last one is more cool...
-------------------
IMPORTANT NOTICE: No trees were killed during the sending of this message but a large number of electrons were terribly inconvienced.
|
|
|
|
|
You can do this in VB.NET
dim MyVar%
which is the same as
dim MyVar as Integer
Anyway, it is just a matter of taste.
For me, I would rather choose between, to .NET or not to .NET.
Sonork 100.41263:Anthony_Yio
|
|
|
|
|
ha ha ha... Your saying could be right in a sense... and No Comments
btw me myself is C then C++ then Java then C# then VB .NET converted creature... so no offenses to everyone
btw, here I remember song of shrek; Bad Reputation; Here, sing with me...
I don't give a damn about my reputation
You're living in the past, it's a new generation
Hey, a girl can do what she wants to do
And that's what I'm gonna do.....
yeeeeee haaaaaaa!!!!!!
ha ha ha...
-------------------
IMPORTANT NOTICE: No trees were killed during the sending of this message but a large number of electrons were terribly inconvienced.
|
|
|
|
|
I don't understand the point about Intellisense not being much good, I see no faults with it, I like the way it displays my XML Comments for my own classes and methods.
For my team C# is the standard (My decision). This was for a few reasons, a big part of which was the much greater supply of documentation and examples already available in C#, but also when looking at other tools, tools such as NUnit, NAnt and NDoc really stand out. Another big influence was the ability for C# and Java developers to understand each others code fairly easily.
Personally, I believe VB.Net was created to keep VB6 developers (of which I was one) from feeling too pissed off at losing the massive intellectual investment they made in becoming experts in their language. I think the initial learning curve going from VB6 to either C# or VB.Net is so great, that it doesn't really matter which language you choose, it will be difficult, but ultimately worth it.
I don't like the way VB.Net has methods that are not part of an object I think this was a decision made partly to please VB6 programmers, and partly to make it look like a different language to C#
Being in a minority of one, doesn't make you insane George Orwell However, in my case it does
|
|
|
|