Configuration: Windows XP Internet Explorer 6.0
|
Hello
Why go with VB.NET? Well, it gives you access to the .NET framework, so you can do a lot more without Declare Lib statements. You also gain access to threads, which was previously the domain of C/C++ programmers. Also, if you want to make online web applications, you can use VB.NET to make ASP.NET sites. Other than that, there's just some cleanup to get rid of the older stuff. (Bye bye, Open For As #) And yes, there is a code converter, but the quality of the conversion depends on how "good" your VB6 code is. |
Hullo,
Switching from VB6 to VB.Net is completely waste of money & time. It is not an upgrade because there are 2 different languages. VB6 is superior to VB.Net is a RAD tool. If you prefer doing more object oriented, choose java or C# instead, since they have better future. |
If you would like to know more about vb.net , refer the follwoing link.
http://vb.net-informations.com suz. |
Hi!
I am also a (ex)VB6 programmer. I've done so many projects and stuffs with it. I was like you: I can easily, fastly, and accurately make projects with VB6. So, why did I switch to VB.NET and C#? When I got my first VS.NET (VS 2005) and took a look at VB.NET, I thought it's only a new upgrade of VB with much much more classes through .NET framework. At that time, I didn't want to switch to a new IDE, I loved so much my old VB6 IDE with all my stuffs (Vista style controls, advanced graphics, registry, system, and data access classes, 1Gb codes samples and hints...). And I tried to create more classes immitated from .NET framework. But I was wrong. VB.NET doesn't only introduces many more classes, but also a new concept of programming (OOP). If you want to switch from VB6 to VB.NET, I don't encourage you to look for a converter or something like that. VB.NET is not so much syntaxically different from VB6. You should re-write your codes and apply the new way of programming (OOP) that the VB.NET offers (see the concept of Object Oriented Programming). Or else, you are wasting your time and the transition will be so bad that it's better to stay with VB6. After programming a while with VB.NET, you'll understand that C# is not as difficult as you heard about. As an ex-VB6 developper, I've found it easier than VB.NET (understanding and coding). Sorry for the long long text... (for your information, I took 2 weeks with one relevant project to switch from VB6 to VB.NET, and 2 days to switch from VB.NET to C#) |
Résultats pour VB6 vs VB.NET
Résultats pour VB6 vs VB.NET
Résultats pour VB6 vs VB.NET
Résultats pour VB6 vs VB.NET
Résultats pour VB6 vs VB.NET