Visual Basic 6: the looming crisis
-
I can't see why? We have an older bug tracking system, written in VB6, and it's running perfectly even on Windows 8...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
I can't see why? We have an older bug tracking system, written in VB6, and it's running perfectly even on Windows 8...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
Quote:
if it relies on obscure COM or control libraries
I'd be guessing that is a fairly low (but measurable) number of VB6 apps. I'd put a guess that anything using hooking might be an issue. Maybe stuff using security APIs as well. Oh Spyworks, I miss you.
TTFN - Kent
-
Quote:
if it relies on obscure COM or control libraries
I'd be guessing that is a fairly low (but measurable) number of VB6 apps. I'd put a guess that anything using hooking might be an issue. Maybe stuff using security APIs as well. Oh Spyworks, I miss you.
TTFN - Kent
Kent Sharkey wrote:
anything using hooking might be an issue. Maybe stuff using security APIs as well.
Can't see why? Windows internals didn't changed a bit since 3.11. Same COM based kernel, same Pascal inspired API...Bring your 'obscure COM' with you - it will run...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
Kent Sharkey wrote:
anything using hooking might be an issue. Maybe stuff using security APIs as well.
Can't see why? Windows internals didn't changed a bit since 3.11. Same COM based kernel, same Pascal inspired API...Bring your 'obscure COM' with you - it will run...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
/shrug. Again, I'm assuming stuff that's now hidden behind UAT, or perhaps stuff that changed between XP and Weven. I'm drawing a blank on what it could be though, and I think I'm still running a few VB6 things at one customer (they look like it anyway).
TTFN - Kent
-
Forget about the crisis. VB6 App goes to the Cloud.Build 2014 @ 3:00[^] Amazing :thumbsup:
-
Kent Sharkey wrote:
anything using hooking might be an issue. Maybe stuff using security APIs as well.
Can't see why? Windows internals didn't changed a bit since 3.11. Same COM based kernel, same Pascal inspired API...Bring your 'obscure COM' with you - it will run...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
The problem is you have to find out what the obscure COM bits that are missing are and find a way to get a hold of them. :sigh:
-
I have an activex component that is still cookin along even in 8.1 :-D
-
Kent Sharkey wrote:
anything using hooking might be an issue. Maybe stuff using security APIs as well.
Can't see why? Windows internals didn't changed a bit since 3.11. Same COM based kernel, same Pascal inspired API...Bring your 'obscure COM' with you - it will run...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
Seriously. And think about some of the windows controls like tree view and how they look the same as Win95 and almost the same as win3.11. Also, isn't it interesting that FileExplorer (Explorer) if pointed at a large repository will spin until it reads every file in the repo (even if there are 10s of thousands) and only after all are read will it begin to display them to you? That is an app in serious need of rewrite and it's the shell. :)
-
Kent Sharkey wrote:
anything using hooking might be an issue. Maybe stuff using security APIs as well.
Can't see why? Windows internals didn't changed a bit since 3.11. Same COM based kernel, same Pascal inspired API...Bring your 'obscure COM' with you - it will run...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
You are joking I hope. The entire kernel is different since Windows 3.11. That was a 16-bit O/S built on top of DOS. Modern Windows derives from Windows NT, an entirely different beast.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
You are joking I hope. The entire kernel is different since Windows 3.11. That was a 16-bit O/S built on top of DOS. Modern Windows derives from Windows NT, an entirely different beast.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
I didn't mean 3.11 literally - my point was that nothing changed since VB6 that should prevent running it on modern Windows... :-D
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
I have an activex component that is still cookin along even in 8.1 :-D
And in April 2014, VB6 has just risen to be the sixth most popular programming language in the Tiobe index. C# is fifth and VB.Net is tenth. And Microsoft "It just works" support continues until 2023. Vote for an updated VB6 at: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221-bring-back-classic-visual-basic-an-improved-versi[^]
