KomuraSoft LLC
Contact
Menu

Windows development & engineering support from KomuraSoft

COM Component DevelopmentConnect the components you rely on to your next app.

Development and maintenance for COM, ActiveX and OCX. We help investigate registration and deployment failures, mixed 32-bit and 64-bit systems, and integration between .NET and C++.

Discuss your COM or ActiveX issue See pricing & process

No specification document needed. Start with what you know.

  • Work directly with an engineer
  • Start before requirements are finalized
  • Commission only the scope you need

You do not need a finished specification

Start with the problem you need to solve.

It works on the development PC, but not at the customer site

We investigate differences in registration, DLL dependencies, permissions and runtime environments.

You need to keep a 32-bit component while updating the app

We compare options such as a separate process and validate an integration approach that fits the constraints.

You need C++ functionality in .NET or Office

We help design and implement the calling interface and integration layer.

Discuss the technical details with the engineer doing the work.

Profile photo of Go Komura

Founder & engineer

Go Komura

A Windows-focused engineer works with you from the initial discussion through investigation, design and implementation. You do not need to have every technical detail worked out before getting in touch.

Experience & technologies / Company information

Published technical article

What Are COM / ActiveX / OCX?

Explore the technical considerations and design approach in this area. These explanatory articles are presented separately from commissioned project experience.

Read the technical article

Scope of support

A focused task or a complete application.

From a specific investigation or change to end-to-end development, we agree on a scope that fits your situation.

COM component design and development

Design and implement COM components for Windows applications, Office and existing systems.

ActiveX and OCX investigation and modification

Investigate and address faults involving registration, bitness, host applications and permissions.

.NET and C++ interoperability design

Compare C++/CLI, COM and separate-process approaches, and design the integration layer for existing functionality.

Examples of results and deliverables

  • Usage conditions and integration approach
  • Component or integration-layer implementation
  • Registration and deployment and validation procedures

These are examples, depending on the work commissioned. We agree on the scope and format of deliverables when preparing the estimate.

Facing a similar challenge? Tell us where things stand.

Discuss your COM or ActiveX issue

No specification document needed. Start with what you know.

Pricing and process

You do not need every detail decided to get started.

Start with the component and its host

You can commission a specific fault investigation or interface improvement, as well as development of a complete component.

Pricing guide

Quoted for the components and work required

We check the calling application, source availability, dependent DLLs, registration and deployment conditions.

Initial feasibility checks and paid engagements

Initial checks needed to assess feasibility and prepare an estimate are generally free, on the understanding that you will commission the full development if it is found feasible. Extended validation, dedicated environments, prototypes, proofs of concept and detailed investigation reports may require a paid engagement.

An investigation or review commissioned in its own right is quoted as a separate paid service. We explain the scope and cost before any paid work begins.

  1. Tell us about the situation

    Share your goal, the problem and the environment, as far as you know them.

  2. Review the scope and cost

    We outline the investigation needed, scope, deliverables, cost and proposed process.

  3. Agree before work begins

    During the work, we share progress, confirmed findings and remaining constraints.

  4. Review the results and handover

    We validate the results under agreed conditions and prepare for deployment or the next step.

Need more technical detail?

Explore technologies and the detailed approach

Connect existing components to the next generation of your Windows software.

Important business or device functionality may remain in an old COM, ActiveX or OCX component. You need it in a new .NET application, but registration or 32-bit and 64-bit differences are getting in the way. KomuraSoft supports the design and development of these connections, along with component investigation and maintenance.

Challenges we can help with

  • Develop a COM component for use from an existing application or Office.
  • Diagnose ActiveX or OCX failures on particular PCs or after deployment.
  • Isolate problems involving RegAsm, regsvr32, registry entries or administrator permissions.
  • Update the application while retaining a 32-bit component.
  • Expose C++ functionality to .NET through a maintainable interface.

Development and investigation we support

New components and changes to existing ones

We design and implement COM components after reviewing the calling application and required interfaces. For ActiveX and OCX changes, we first investigate the usage conditions and dependencies.

Registration, deployment and operating environments

We review registration, DLL dependencies, permissions, the host’s 32-bit or 64-bit architecture and threading model. We consider Reg-free COM where applicable, along with deployment and configuration procedures that can be reproduced at the installation site.

Connecting .NET and C++

We compare C++/CLI, COM-based integration and separate-process architectures. The design considers both retaining the existing component and keeping the new side maintainable, making the integration layer’s responsibilities and constraints explicit.

How an engagement proceeds

  1. Confirm usage conditions. Identify the host, component, source availability, registration and deployment environment.
  2. Validate the integration approach. Compare continued use, an integration layer, a separate process and gradual replacement.
  3. Implement and prepare deployment. Within the agreed scope, verify registration, distribution, permissions, logging and rollback as well as operation.

Planning a wider application migration?

This service centers on components and their interfaces. For the overall approach to retaining and migrating multiple assets, see legacy asset reuse and migration support.

Share the names of the applications or components, the error and any known 32-bit or 64-bit configuration. When the architecture is unclear, we can start by identifying it.

Questions before commissioning work

Can you help when we cannot replace old COM or ActiveX components yet?

Yes. We examine behavior and dependencies, then separate continued use, interface changes and replacement. A complete rewrite is not assumed.

Can you work with mixed 32-bit and 64-bit environments?

Yes. We check the host application and component architecture and consider approaches such as separate processes. Re-registration alone may not solve the issue, so we validate an approach against the actual usage conditions.

Can you investigate components that work in development but fail after deployment?

Yes. We compare registration, dependent DLLs, permissions, the calling application and deployment methods. After establishing reproduction conditions, we address the fault and review the installation procedure.

Get in touch

A few lines about your situation are enough.

You do not need a detailed specification or technical terminology. Share what you know about:

  • The problem or the outcome you need
  • The software, devices and operating environment
  • Your preferred timeframe, even if it is not decided

There is no need to send confidential documents or passwords with your initial inquiry.

Example inquiry

An existing ActiveX component does not work on some PCs. Could you investigate the cause, including registration and the 32-bit and 64-bit configuration?
Discuss your COM or ActiveX issue Send an email

No specification document needed. Start with what you know.

The discussion button opens our English contact page with ways to get in touch. “Send an email” opens a draft with the service name and blank prompts for your inquiry.

Browse related technical articles