Should I move to VB.NET?

[plsoft]

Do i need to master visual basic 6 to learn vb.net, or is it enough to have just a basic knowledge? Moreover, do you think visual basic 6 has a future? Or should i move to VB.net?

[mendhak]

Moreover, do you think visual basic 6 has a future?

Moreover, no.

[Hack]

Do i need to master visual basic 6 to learn vb.net

No

or is it enough to have just a basic knowledge?

Not needed.

Moreover, do you think visual basic 6 has a future?

Yes, and it is all bad

Or should i move to VB.net?

Yes. Oui. Ja. Si. I wish I knew how to say YES in more languages.

[RhinoBull]

Moreover - Sim, Да, Ναι, はい, 그렇습니다, 是 ......

Moreover, if you don't have it yet then download a copy of Visual Studio .Net 2005 Express Edition today (it's free) and stop wasting your time.

[plsoft]

Thanks a lot guys, will do as advised.

[RhinoBull]

Good luck.

[Hack]

We do have a VB.NET forum section should you have questions once you get started.

Some very knowledgable, world class programmers, stalk the halls of that part of VBF so I'm certain you will be able to get the assistance you need.

[Grimfort]

Its a shame I am not one of them .

[RhinoBull]

Its a shame I am not one of them .

The future is all yours - work hard if you want to become one.

[BodwadUK]

You should only really use VB6 if you working alongside or with VB6 apps. New projects are best started in .net as it increases their lifespan.

When I can I try to use VB.net, but I am still learning it and what changes they have made, sodding frames, files and shapes get me!!! Why did they remove the shapes? I loved them. And the new 'Frame' or groupbox is a pain in the rear end

[Atheist]

NoNot needed.Yes, and it is all badYes. Oui. Ja. Si. I wish I knew how to say YES in more languages.

Ja. That is swedish! Go sweden!

[penagate]

Do i need to master visual basic 6 to learn vb.net

No.

is it enough to have just a basic knowledge?

No.

Moreover, do you think visual basic 6 has a future?

No.

Or should i move to VB.net?

No.

[Atheist]

No.

No.

No.

No.

If you think that VB6 has no future, why dont you think he should move to .Net?

[grilkip]

If you think that VB6 has no future, why dont you think he should move to .Net?

VB.NET

.NET

Not the same thing.

[RhinoBull]

VB.NET

.NET

Not the same thing.

Yes, technically you're right.
However, since programming language in .Net is not relevant then that was more or less appropriate way to say.
But more importantly - everybody understands that anyway...

[CVMichael]

Yes. Oui. Ja. Si. I wish I knew how to say YES in more languages.

http://www.freelang.net/expressions/yes.html

[Seraphino]

Well, lets just say that VB.NET is the retarded cousin of C#.....if anything move to C#, cause if you know VB, C# is very easy to pick up.

[RhinoBull]

Well, lets just say that VB.NET is the retarded cousin of C#.....if anything move to C#, cause if you know VB, C# is very easy to pick up.

Just out of curiousity, Seraphino, how much of either language do you know?

[Seraphino]

Well, I know tons of VB.NET because for a fact I did use it for a while. But I have been using C# for over a year now, and I know everything about it except for things like Web Services.

[RhinoBull]

Well, I know tons of VB.NET because for a fact I did use it for a while...

Aha... So if you "did use it for a while" then you should know that .Net isn't about which language to use - it's all about the Framework itself. Programming language isn't relevant anymore (again, in .Net framework).

Also (and with all do respect) "use it for a while" doesn't necessary means "know it" ...

Best regards.

[Seraphino]

know that .Net isn't about which language to use - it's all about the Framework itself.

I am just curious. Are you saying that calling it "VB.NET" is a bad thing, or shows something? I don't quite understand what you are saying when you say that.

[RhinoBull]

That was direct reply to one of your "statements" :

...lets just say that VB.NET is the retarded cousin of C#...

In my opinion that is a pure nonsense. Sorry.

[Seraphino]

Everyone has a right to their own opinion

[Atheist]

slightly off topic but I just want to slip a line into this c#/vb .net discussion.
The other day, I sat by my computer thinking "hey, why not move to c#!".
So I downloaded visual c# express, and after 10 minutes of case sensitive *bs* and semicolons I finally realised why I never moved to using c# before And I wont touch it again.
So therefor, I think that if plsoft would like to move to any of the .Net languages, he should go for VB .Net since he know VB6 from before so he wont be pulling his hair over what i mentioned above.


and btw...is it only me, or is the error list in the C# IDE...rude?

[RhinoBull]

Syntax is matter of taste and habbits I guess.
You know, personally I hate case sensitive environment and since I "moved" from everyday C++ development long ago to VB world I didn't miss a C type syntax for a single minute. But again, it's a matter of personal preferences. Some friends of mine can't live without it [the C type syntax] so they write in C#.

[penagate]

I have been using C# for over a year now, and I know everything about it except for things like Web Services.

Then you'd know enough to have not made that comment since web services are a language-independent technology. Next!

[RhinoBull]

Then you'd know enough to have not made that comment since web services are a language-independent technology. Next!

... and one of the simplest things to do ...

[penagate]

So I downloaded visual c# express, and after 10 minutes of case sensitive *bs* and semicolons I finally realised why I never moved to using c# before And I wont touch it again.

I don't understand. After 10 minutes of using C# for the first time, you realised why you had never used it before?

So therefor, I think that if plsoft would like to move to any of the .Net languages, he should go for VB .Net since he know VB6 from before so he wont be pulling his hair over what i mentioned above.

Yes... because you didn't understand it, decided you didn't like it, and it's therefore a bad thing.


I love these language 'debates'. You don't "move" to a language; it's not like getting married, you don't have to be faithful to one partner. I say this every time and I'll keep saying it: a language is just a tool, and you use the best tool for the job. As you gain experience programming, you add more tools to your toolbox. In this case, we are discussing .NET; whether you prefer C# or VB is irrelevant, since they are both .NET languages and do the same thing. As Rhino said, it's just syntax, and subjective. C# does some minor things slightly better and VB does others, but on balance, they're equal.

VB 6, on the other hand, is old, and .NET is its replacement. You can throw away the old hammer and put in the new electric cordless 3G WiFi one with built-in camera. But you never pick out a tool without first thinking which one is best.

[RhinoBull]

... it's not like getting married...

Quite often it's more than that I'm afraid - it has to support your marriage.

[rory]

VB 6, on the other hand, is old, and .NET is its replacement.

according to Microsoft .. and their fan club.

[Atheist]

But wouldnt you agree that coming from VB6, VB .Net would be the easiest step into the object oriented "world"?

I know its all a matter of taste, I just didnt think it was against the forum rules to post personal thoughts

I don't understand. After 10 minutes of using C# for the first time, you realised why you had never used it before?

Yes because Ive done c++ at school a while ago, and immediately when looking at c# it brought back the old painful memories.

Yes... because you didn't understand it, decided you didn't like it, and it's therefore a bad thing.

understand what? Doesnt one always decide what they dont like? I dont really understand that, I decided I didnt like it because I simply...didnt like it

You don't "move" to a language

Yes you do, If you want to.

[Besoup]

Aha... So if you "did use it for a while" then you should know that .Net isn't about which language to use - it's all about the Framework itself. Programming language isn't relevant anymore (again, in .Net framework).

Also (and with all do respect) "use it for a while" doesn't necessary means "know it" ...

Best regards.

I am also looking to make the jump from VB6 to VB.NET. Do you have any links handy that might easily explain how the .NET framework works. I find it interesting that you say that the language you use is irrelevant, just looking for some more info.

[RhinoBull]

according to Microsoft .. and their fan club.

I sometimes wonder rory, what in the world are you doing on this board?
We are Microsoft oriented forum and even name "tells" you that explicitly.
If you dislike it so much then maybe it's time for you to find another (more suitable for your taste) forum but please stop saying that.

Thank you.

[RhinoBull]

I am also looking to make the jump from VB6 to VB.NET. Do you have any links handy that might easily explain how the .NET framework works. I find it interesting that you say that the language you use is irrelevant, just looking for some more info.

Well, you may want to read article below:

Microsoft .Net Framework Getting Started

Also, regarding languages in the framework: in a nutshell any language available in the .Net is based on CLR (Common Language Runtime) and therefore they all have access to the same libraries.
Before the .Net each language had its own framework (so you know VB6 has msvbvm60.dll) due to COM architecture and that was a major pain.

[rory]

I sometimes wonder rory, what in the world are you doing on this board?
We are Microsoft oriented forum and even name "tells" you that explicitly.
If you dislike it so much then maybe it's time for you to find another (more suitable for your taste) forum but please stop saying that.

Thank you.

This is a VB forum, doesnt mean we have to all kisss MS's butt.
You can bend over all you like though.

Dont get personal with me and I wont get personal back.

[RhinoBull]

This is a VB forum.

Exactly right.

[BodwadUK]

This is a pointless argument guys