Why Your Silverlight and VB6 Applications Are Ticking Time Bombs

Why Your Silverlight and VB6 Applications Are Ticking Time Bombs

Aging VB6 applications are a time bomb. Not only are the hardware, operating systems and runtime environments that they run on all candidates for replacement, but Microsoft will almost certainly drop support for VB6 after Windows 7. When the underlying infrastructure gets replaced, it could mean your application suddenly stops working — i.e. blows up — and you won’t be able to call on Microsoft for help.

We like to dismiss the proverbial “legacy application” — like that old VB6 app — as something from the dinosaur age. It’s easy to write off pre-Y2K (year 2000) programs, MS DOS, COBOL and mainframe systems with a cynical smirk while ignoring the millions of lines of code making up today’s client/server systems, but these often critical applications really are time bombs. Paradoxically, even the applications written in more recent technologies such as Silverlight and Web Forms are also in danger of blowing up.

Editor’s Note: The author, Navot Peled, is co-founder and president of Gizmox, makers of the migration tool for legacy client/server applications. We have selected this article for publication because we believe it to have objective technical merit.

The HTML5/JavaScript Revolution Leaving Silverlight as a New Time Bomb?

Microsoft’s technology roadmap has taken some sharp turns in direction. ASP.NET/Web Forms was scrapped in favor of Silverlight and now, after converting developers and enterprises, it’s shifted its focus yet again. That isn’t a bad thing in itself; the problem for developers is the lack of support for backward compatibility or the lack of a migration offering. For example, Microsoft still hasn’t come up with a true migration tool for VB6, either to .NET or a Web architecture.

Even with such roadmap changes taken into account, it’s difficult to envision the next Windows platform not supporting .NET, even though Microsoft has not yet issued a definitive statement to that effect. The bigger concern is which plumbing infrastructure .NET developers are supposed to use for Web applications. The horse that Microsoft has been backing since the summer of 2007 — the ASP.NET/Silverlight cocktail — seems to have lost its momentum. In a Win8 shell preview at the D9 Conference earlier this year, HTML5 and JavaScript were ominously presented as Microsoft’s future Web strategy, with Silverlight not getting a mention.

It would be reasonable to assume that this is not unconnected to the tremendous following already attained by HTML5 and its semi-official engagement with JavaScript. If their popularity continues to spread like the Facebook revolution, it’s likely to overthrow all proprietary plug-ins, including the ubiquitous Adobe Flash/Flex, which has led the rich browser user experience since it was under the Macromedia label.

Like Flash/Flex, Silverlight is locked out of Apple’s iOS, whose use has spread dramatically in the iPad/iPhone age. Silverlight isn’t supported by Android either. The ace in HTML5’s deck is cross-platform compatibility (browser and OS), and that raises a serious question about Silverlight’s chances of survival. The relative lack of information from Microsoft doesn’t alleviate these concerns either.

The Impending VB6 Bombshell

VB6, together with the users of its applications, looks to be the first major Win8 casualty looming, as it’s almost certain that VB6 won’t be supported beyond Windows 7. It has been extended repeatedly since 2005 and if it couldn’t be embraced by .NET with an automatic migration tool, there doesn’t seem much chance of a place for it in the HTML5/JavaScript/64-bit Win8 ecosystem.

Companies relying on VB6-based information systems — by some estimations, around 15 billion lines of VB6 code are running in enterprises — are those most in need of modernization to rich Internet applications. A number of hacks and workarounds will no doubt keep the VB6 runtime working under Win8 even without Microsoft’s support, but the inability to further develop the VB6-based systems on the new operating system –at least not using current technologies or tools to support new or even some core Win8 capabilities — makes this approach futile for line of business (LOB) applications.

Choosing a New Lease on Life Over Retirement

Given that Microsoft’s declared Web client strategy is HTML5/JS and not a proprietary format, we can presume their future Web solution will be without WPF or Silverlight. Ideally this would be:

  • A server-centric architecture based on .NET
  • An HTML5/JS/Ajax framework as the presentation layer
  • Form-like development in Visual Studio
  • Very high virtualization of presentation layer and data binding
  • Available now on 32/64-bit Windows
  • 100% supported in Win8
  • Supplied with a powerful migration capability of current (legacy) systems to Web-based systems

Owners and developers of both client/server and Web-based LOB systems should be looking for ways to modernize their applications to a robust server-based Web architecture with an HTML5/JavaScript client. This way, they will ensure their systems are not running in an environment that might go up in smoke when the clock stops ticking.


About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist