- Messages
- 64
- Country

Frank,
I know this is tangental to this thread (Moderators you may wish to move any posts to another thread), but you are right. VB.NET is a totally different animal and requires new knowledge. The generated code is readable enough, but writing it is another issue. In my working life I was designing strategies to find the most cost-effective way to move legacy VB4,5 and 6 code into VB.NET and found that the traditional programmers who had originally written the application really struggled in converting to the new programming style. Without the requisite training the learning process was arduous and s/w was poorly written.
By comparing the effort employed by trained but inexperienced developers against experienced traditional developers I found that the new boys returned a better product which was easier to maintain and took less time in on-going support as it was object oriented and therefore more modular whilst the traditional was just one (or a few) large programs which after amendment or enhancement needed 5 times more testing effort and debugging. Costs were in the millions rather than the expected (by the board) tens of thousands.
My ex-wife told me recently that the lack of training has now bitten back as VB6 usage has now been discontinued and only 20 of the 120 small system developers are 'fluent' in .NET.
Yea and it's all a bit much for this old truckie Come part time dabbler in programing.







