Linked by Thom Holwerda on Mon 11th Jun 2012 00:38 UTC, submitted by judgen
Windows "Microsoft recently extended 'It Just Works' compatibility for Visual Basic 6 applications through the full lifetime of Windows 8. Visual Basic 6 first shipped in 1998, so its apps will have at least 24 years of supported lifetime. Contrast that with the Microsoft .NET Framework 1.0 (2002), which is incompatible with Windows 7 (2009)."
Thread beginning with comment 521525
To read all comments associated with this story, please click here.
It just works?
by Alfman on Mon 11th Jun 2012 02:23 UTC
Alfman
Member since:
2011-01-28

Sharing my experience, I actually have several programs I had written in VB6 several years back. For sentimental reasons I'd like to run them again but unfortunately many won't run anymore.

One that I worked on during a collage break was a poor amateur clone of the "7th guest". The 7th guest took place in a raytraced house, mine took place in a real house using a video camera. Now all I can do is play the individual video clips, the VB6 game doesn't work.

For work I also needed to maintain a legacy VB6 app, but the COM Control component (which came with VB6 itself) had licensing issues and refused to install on the client's machine. MS's application deployment wizard failed to install the component too. In the end we threw our hands up and installed an unlicensed copy of VB6 itself on the client machine, which installed all COM Components in developer mode without restriction. I wonder how often DRM causes problems for people legitimately running legacy software?

Reply Score: 4

RE: It just works?
by kwan_e on Mon 11th Jun 2012 02:57 in reply to "It just works?"
kwan_e Member since:
2007-02-18

What people seem to miss about the "It Just Works" slogan is that they're putting the emphasis on the wrong word. It should be "It -JUST- works".

As in "My shot -JUST- missed his head".

Reply Parent Score: 9