Firstly, there are different versions of visual basic.
Although VB.Net and VB6 are supposedly versions of visual basic, they are really very different.
From language perspective, VB.Net is VB6 structured in the C# structure.
So if your boss is an expert in VB6, there is still a learning curve for him when migrating to VB.Net.
According to internet sources, VB6 is more popular than VB.Net.
From implementation perspective, there are options so that VB6 programs can be compiled to native code.
VB.Net programs on the other hand requires the.Net framework. That means the computers must be of
certain calibre so that the.Net framework requirements can be met. If you are migrating the new programs on existing computers, there is a high chance that these computers will need upgrades/replacements.
Whether visual basic (VB6 or VB.Net) is suitable for a project is actually dependent on the nature of the project and the client. Below are some of the characteristics of visual basic I can think of. I have also put in pointers for Java as it is currently one of the most popular language.
(1) VB is good for prototyping. Screen changes can be made within minutes.
There are IDEs for Java to support GUI design but not as seamless as VB.
(2) VB is good for both non-programmers and programmers.
The syntax is fairly simple to understand and there is no need struggle with OO concepts.
Err...well VB.Net is actually OO. Hence VB.Net is harder to learn than VB6.
Java programmers need to know OO concepts just like C programmers need to know pointers.
(3) VB is not so good when high performance is required (games/encryption...etc).
It's not designed for that.
(4) VB is not so good when very fine control is required.
(eg. programming of window components, COM objects, communication objects...etc)
(5) VB is only usable on Microsoft platform. VB.Net is only usable on Microsoft.Net platform.
It is possible to use Mono for linux platform but it is not a safe bet..Net framework is not native in WinXP and need to be installed separately.
This is just like downloading Java runtime and installing it to run the Java program.
(6) VB programs can do automation (eg. invoke an Excel spreadsheet from your program...etc)
on the Microsoft platform.
(7) VB6 is coming to the end of life. VB.Net is less matured compared with VB6.
Compared to VB6, VB.Net is much lacking in both content and accuracy in the documentation.
Java is a matured product compared to VB.Net and has more in both content and accuracy
in the documentation.
(8) If VB.Net is used, please avoid SOAP calls. They degrade performance.
For big projects, the overhead will be significant.
(9) If the older application uses Window DNA, it is likely to be easier to migrate to VB.Net.
Otherwise, the team may want to explore alternatives and weigh pros and cons.
Afterall, VB is not the only choice on the Wintel computers.
Hope these information will be useful.
Slashdot Mirror
Firstly, there are different versions of visual basic. Although VB.Net and VB6 are supposedly versions of visual basic, they are really very different. From language perspective, VB.Net is VB6 structured in the C# structure. So if your boss is an expert in VB6, there is still a learning curve for him when migrating to VB.Net. According to internet sources, VB6 is more popular than VB.Net. From implementation perspective, there are options so that VB6 programs can be compiled to native code. VB.Net programs on the other hand requires the .Net framework. That means the computers must be of
certain calibre so that the .Net framework requirements can be met. If you are migrating the new programs on existing computers, there is a high chance that these computers will need upgrades/replacements.
Whether visual basic (VB6 or VB.Net) is suitable for a project is actually dependent on the nature of the project and the client. Below are some of the characteristics of visual basic I can think of. I have also put in pointers for Java as it is currently one of the most popular language.
(1) VB is good for prototyping. Screen changes can be made within minutes.
There are IDEs for Java to support GUI design but not as seamless as VB.
(2) VB is good for both non-programmers and programmers.
The syntax is fairly simple to understand and there is no need struggle with OO concepts.
Err...well VB.Net is actually OO. Hence VB.Net is harder to learn than VB6.
Java programmers need to know OO concepts just like C programmers need to know pointers.
(3) VB is not so good when high performance is required (games/encryption...etc).
It's not designed for that.
(4) VB is not so good when very fine control is required.
(eg. programming of window components, COM objects, communication objects...etc)
(5) VB is only usable on Microsoft platform. VB.Net is only usable on Microsoft .Net platform.
It is possible to use Mono for linux platform but it is not a safe bet. .Net framework is not native in WinXP and need to be installed separately.
This is just like downloading Java runtime and installing it to run the Java program.
(6) VB programs can do automation (eg. invoke an Excel spreadsheet from your program...etc)
on the Microsoft platform.
(7) VB6 is coming to the end of life. VB.Net is less matured compared with VB6.
Compared to VB6, VB.Net is much lacking in both content and accuracy in the documentation.
Java is a matured product compared to VB.Net and has more in both content and accuracy
in the documentation.
(8) If VB.Net is used, please avoid SOAP calls. They degrade performance.
For big projects, the overhead will be significant.
(9) If the older application uses Window DNA, it is likely to be easier to migrate to VB.Net.
Otherwise, the team may want to explore alternatives and weigh pros and cons.
Afterall, VB is not the only choice on the Wintel computers.
Hope these information will be useful.