|
-
Dec 9th, 2018, 01:31 PM
#11
Re: No troll. What are the (legitimate) reasons people are still using VB6 ?
 Originally Posted by RipVoidWinkle
Yes, my projects are small and I made it clear that I understand the complexity of migrating legacy code.
For me, it came down to having to use Win8 at work, so I had to move to VB 2005 many years ago.
But, if you think VB6 can do everything .NET can ....you are missing the OOP paradigm.
I'm not really sure you know what that means in this context. No offense. You had thought that VB6 didn't run on newer OS. This is absolutely false. You simply didn't uncheck the additional options during setup, and that caused installation to fail, for you.
Expert programmers will be utilizing the most efficient tool to do the job, whether that is VB6 or VB.NET. There is no room to polarize one way or the other, when efficiency for the individual is the dominant factor.
VB6 is an underutilized OOP language, however there may be web related features in vb.net that supercede VB6's web features.
In fact, there are things that VB6 can do that VB.NET cannot do, ever. For example, when making an unattended OS CD a VB6 application will "just work" early before the .NET framework has had a chance to install. In general over time, VB6 has been more robust with a close relationship to VBA and VBscript. This direct relationship with VBA and Office is another reason why VB6 will not die anytime soon.
Speed is also a factor that VB.NET cannot duplicate, and as it turns out this can cause security issues in the application if designed in VB.NET, while the same application designed in VB6 does not have the same delay issues that cause this type of vulnerability.
Last edited by TTn; Dec 9th, 2018 at 01:37 PM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|