The Challenge of ActiveX -- Visual Studio Magazine

Desmond File

The Challenge of ActiveX

Earlier today we reported on the release of TX Text Controls ActiveX 16.0, a collection of word processing components for ActiveX app development. The new release brings the ActiveX control suite to par with previously released WPF and Windows Forms versions of TX Text Controls 16.0.

For Bjoern Meyer, vice president of product management at component maker Text Control GmbH, the decision to release an ActiveX port of its latest TX Text Controls package was a simple matter of customer demand.

"Overall, we delivered more than 40,000 licenses of TX Text Control. A significant part [of that] was ActiveX and these legacy applications are still maintained," Meyer told me in an email interview. "People need newer document formats such as DOCX or PDF/A, so a newer release is required."

Meyer is quick to point out that many companies developing ActiveX-based applications are looking to move to .NET. And for good reason, Meyer said, noting that Microsoft "moved Visual Basic 6.0 out of extended support starting in 2008." He also added that the 32-bit VB6 runtime files and ActiveX controls may not be supported by newer versions of Windows.

"From a developer point of view, I would do everything to move to .NET as soon as possible," Meyer said, adding that his company offers free migration support to help move customers from ActiveX to .NET.

"Do I think that all applications with several millions of lines of code will be ported to .NET in one or two years?" Meyer asked. "Of course not. That takes time and costs a lot of money. Especially, because porting applications from one to the other technology is nothing innovative."

Meyer continues: "At the end of the day, you [end up with] the same functionality but on a different platform. No, the reasons must be somewhere else. .NET is a future-oriented development platform and it is easier to maintain later. But it is crystal-clear: Porting the code to .NET is very expensive, but not doing it could kill your business.

Are you currently supporting ActiveX applications? If so, how are you going about managing the platform challenge?

Posted by Michael Desmond on 01/26/2011

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.