Quote Originally Posted by Phill.W View Post
Elroy,

"Business Continuity" or any Risk of its failure is really, really important to Business People.
Having a company that is "solid" and "dependable" (Hah!) to whom they can run if and when it Hits the Fan, gives them a Warm and Fuzzy Feeling of security.

Consider this: There is absolutely nothing to stop Our Friends in Redmond from putting out some Security Patch or whatever tomorrow that completely deep-sixed VB6.
It's not even on their "radar" of things to think about not breaking any more and hasn't been for two decades, now.
OK, it hasn't happened yet, but if it did, many companies would lose huge swathes of their software base. For a while, they might be able to "pull" that particular update but, eventually, things like CyberEssentials will be kicking down the door demanding that things get patched up properly (or those companies won't be allowed to bid on such and such Business opportunities) and, at that point, hard cash would win out and VB6 would finally go to the wall.

The only Good News in all that would be the sudden, huge demand for Developers who still know VB6 and can re-write it into "Latest-and-Greatest-Thing .Net". Does anybody else remember the heady days of the late Nineties, rapidly hacking COBOL code to make it "Y2K-compliant"?

Regards, Phill W.
And there would likely be a HUGE protest from many organizations along with a move to earlier operating system versions for those who could get by with that. It really isn't much effort for Microsoft to continue to support the core VB6 runtime and they would be shooting themselves in the foot even now by breaking it. And there are still many who HATE so-called managed code and wnt nothing to do with it due to the JIT compiler, bloated framework, ease of decompiling, etc.....