Topic

ActiveX / Migration Topic

Topic page collecting ways of thinking about maintenance and migration, and related pages, for people unsure whether to keep or replace ActiveX / OCX.

What this topic is meant to organize

Projects with existing ActiveX / OCX assets often look like a false choice between rewriting everything and touching nothing. In practice, there are many options in between.

  • keep the current component and maintain it
  • wrap only the outside so newer code can handle it more easily
  • replace surrounding parts in stages
  • sort out only the native boundary with a separate approach

Points that often come up in consultations

  • how long should an existing ActiveX / OCX asset be kept alive
  • how should newer .NET code interact with it safely
  • which parts should be replaced now and which should stay for the moment
  • how should COM responsibilities and thread boundaries be separated

Typical direction

It is often more effective to clarify the current boundaries first and decide where maintenance, wrapping, or staged replacement makes sense than to jump straight to a full rewrite. Reading the technical consulting page, the migration support page and the related articles together makes it easier to compare approaches.

Consult Us Here

If this page is close to the situation you are dealing with, please consult us and include the current context and what kind of support you need.

Back to Home