VB 6.0 Vs VC++ 6.0

VC6 was never really made for doing windows apps with the ease of VB. Whether you want ot learn VC6 is completely up to you... and depends on our needs, but now days I (personally) won't bother with it too much.

VB6 works nicely for quickly developing front ends... but they'll be slow.

The whole .NET architecture allows you to program so much more so much quicker. So, as far as development time goes, it just can't be beat. But there is a trade off in speed (another level of abstraction is always slower)... and Computers have to have the .NET framework enabled to run your progam. (I don't think the second problem is too bad, as I'll bet future versions of windows will have the CLR (i.e. .NET framework) embedded... So, in time the problem will pass. And who knows maybe someone will develop a .NET framework for linux... well one can live in hope.)

The C++ (i.e. VC7) included with VS .NET 2003 is far more ANSI C complient than VC6, so from that point of view, it is better too. C++ is always fast (unless you're an idiot when programming) but development time is much longer. Even once your thinking C++ it still takes longer because there is just more code to write and test.

Generally one can say there is a trade-off... I have often quoted this statement:
"You can have it quick OR you can have it quickly."

Learn How to do OOP ActiveX programming in VB 6.0 instead migrate from VB 6.0 to VC++ 6.0
VB is dying:thumbd:
And learning any kind of C family language can be beneficial.
And who knows maybe someone will develop a .NET framework for linux... well one can live in hope.
Its already done!
Look for "mono" project :D

The whole .NET ....But there is a trade off in speed (another level of abstraction is always slower)Not much - and there are some cases when it is not true!

Visual C++ is quite strange, :confused: - Im loving it:D
Try to write applications, struggle, continue - at the end it's worth it :thumb:
And that's the spirit!
I agree :) .

but does the high performance have a real value ? Very often - YES!!!!

Suppose application X written in C++ performs task T in 30 milliseconds and application Y written in VB performs the same task in 90 milliseconds the user will not even notice the difference.VB 1 second - and it is a difference that user usually feel and complain about.

Ive done many projects in VB and many times VB was so slow that I have to write C dll or ActiveX to speed things up. And thats the reason to hate it very much.

I also were forced to do some dirty tricks with COM to achieve multithreading in VB. :sick: Brrr...

That much variation in performance is never due to the programming language used. Even if it's Java And why all desktop programs are not written in Java - because Java made user interface is so slow that users get furious when they forced to work with it.

Yes VB is better (when speeking about performance only) than Java, but not very much :thumbd: . In Java U can do almost anything in pure Java (which is not the case for VB) and is multi -platform. So overall if I have to choose ... I will chose Java but since I have wider options I choose C++ and C# :p

Best regards,
Krzemo.

Well, quite frankly, you'll find C# .NET and VB .NET are the same language (just different words). So it doesn't really matter too much... but better to get used to C# rather than VB. Its far more the "industry standard" than VB for .NET programming.

DEFINITELY learn about OOP. How you managed to get along this far with out it I don't know. OOP is not going to go away any time soon, and is definitely the industry standard. Most big systems are written using OOP.

C++ is a pretty much a "must have" in industry. Its fast and its slick... It's probably one of the fastest high-level languages there is. (It is faster than C#. Always!! If it is slower then it is inefficient coding on the users side, not C++ that is slow... it all comes down to abstraction layers. That said... often half the problem with slow programs is inefficient coding and so C# does, to a certain degree, limit this.)

C# is quickly catching up with C# as a "industry standard". The time to market using C# is unbelievable. (This from a guy who spent a good protion of last night hitting his head against wall typing to do basic type conversion... which in C++ is just sooooo easy, but in C# requires a lot of coaxing.)

I see myself getting crucified for this next statement but here goes: With the advent of C#, JAVA will die (YEAH)... as C# basically fulfills what was it's market roll... It (JAVA) will still be used for cross-platform development for a while, but sooner or later it will fall away as C# and the .NET framework becomes more widely accepted. JAVA is just too dang slow.

In a nutshell my opinion of the way things are going is:
Soon the standard way of writing apps will be C++ backends (i.e. do all the work) and C# frontends (GUI). Its pretty much already this anyway.

VB.NET / C++ .NET / C#?
C++ and C#. Don't worry about VB .NET

explore C++ to help myself to learn C# or just jump to C# directly
Learn C++ for the sake of knowing C++. Don't worry about visual side of it though.
Learn C# as well. It really falls into place (mostly) once you know C++ though.

Get more VB 6.0 for now then jump to VB.NET
Na. Make the switch now.