Join 300,329 Programmers for FREE! Get instant access to thousands of experts, tutorials, code snippets, and more! There are 1,838 people online right now. Registration is fast and FREE... Join Now!
I think its about time Microsoft killed the support for vb6 in the vb.net langauge. vb.net is consider to be runt of the programming languages (professionally) because it has the monkier VB.
i don't know about VB6 but i know that the old versions are expiring and VB6 is about 1998 11 years ago and i think Microsoft will not Give Supports to VB.Net, hmmmm.... maybe yes but i'm 99% sure that No.
You do know that vb.net its still possible to use vb6 functions and routines, through the Microsoft.VisualBasic Namespace. I'm saying that this should be removed. Also they should remove the vb migration functionality. The vb6 to vb.net code converter.
This post has been edited by AdamSpeight2008: 7 May, 2009 - 01:02 AM
You do know that vb.net its still possible to use vb6 functions and routines, through the Microsoft.VisualBasic Namespace. I'm saying that this should be removed. Also they should remove the vb migration functionality. The vb6 to vb.net code converter.
I personally feel support for legacy VB6 functions should have ended with the release of .Net Framework 1.1. I feel that should have given programmers enough time to get used to using the new language and libraries. There's nothing more irritating than looking through someone's VB.NET code and seeing a ton of legacy functions being used (such as Mid, Left, Instr, etc).
Come on people, VB.NET has been out for quite some time now, and the native libraries have been there for a long time for a reason.
I personally feel support for legacy VB6 functions should have ended with the release of .Net Framework 1.1. I feel that should have given programmers enough time to get used to using the new language and libraries. There's nothing more irritating than looking through someone's VB.NET code and seeing a ton of legacy functions being used (such as Mid, Left, Instr, etc).
Come on people, VB.NET has been out for quite some time now, and the native libraries have been there for a long time for a reason.
no use of keeping old technologies ,its just a burden to students,some universities prefer to keep the old syllabus
I think its about time Microsoft killed the support for vb6 in the vb.net langauge. vb.net is consider to be runt of the programming languages (professionally) because it has the monkier VB.
vb.net <> vb6
if anything its vb.net > vb6
What are your views?
Yes, vb.net > vb6
unless you want to write a native application for an older platform that does not support .NET. Why you would want to write for an older platform, I don't know.
So if you are targeting Windows you might as well use .NET and forget about vb6.
I would completely agree that the legacy functions should be removed. There are already not that many developers who are switching from VB6 to VB.NET since .NET already became a industry standard, replacing the old versions of VB. Legacy functions just keep developers that used VB6 from learning the new .NET functions and classes.
I think its about time Microsoft killed the support for vb6 in the vb.net langauge. vb.net is consider to be runt of the programming languages (professionally) because it has the monkier VB.
vb.net <> vb6
if anything its vb.net > vb6
What are your views?
I couldn't disagree more! There are plenty of VB6ers out there who still have not migrated to .net. I think it might be a good idea to have this support as an option when installing. Guys that have made the switch sucessfully don't need it. I am only just getting to grips with VS2005. You wouldn't deprive me of an income would you ?
Well if you've made the jump to VB.NET then the need for legacy functions should be gone, and should have been gone with version 1.1. If you need legacy functions to make a living maybe you should look at why you need them
Maybe because his company does. Yes, there are some out there that still want vb6. Not the majority, but some. If removing the reference to it in your project properties ia all you need to do to make yourself happy, why mess with someone else's livelihood.
I don't use it (vb6) anymore, so I don't really care if it stays or not, but I guess I don't really see what the difference is.
Forum Index:
Programming Help |
C and C++ |
VB6 |
Java |
VB.NET |
C# |
ASP.NET |
PHP |
ColdFusion |
Perl and Python |
Ruby |
Databases |
Other Languages |
Game Programming |
Mobile Development |
Software Development |
Computer Science |
Industry News |
Programming Tutorials |
C++ Tutorials |
Visual Basic Tutorials |
Java Tutorials |
VB.NET Tutorials |
C# Tutorials |
Linux Tutorials |
PHP Tutorials |
ColdFusion Tutorials |
Windows Tutorials |
HTML/JavaScript Tutorials |
CSS Tutorials |
Flash Tutorials |
Web Promotion Tutorials |
Graphic Design & Photoshop Tutorials |
Software Development Tutorials |
Database Tutorials |
Other Language Tutorials |
ASP.NET Tutorials |
Game Programming Tutorials |
WPF & Silverlight Tutorials |
| 
