Announcing Our Technical Blog - A Windows / C# / COM Development Blog

· Updated: · · Announcements

Revision history (1 updates, last updated Sep 1, 2026)

A log of the changes made to this article. Where a pre-update version was archived, it stays readable at a permanent DOI link.

Retranslated as a full translation of the Japanese original. The previous English version was an abridgement that carried only part of the source, so sections, tables, Mermaid diagrams, figure captions and FAQ entries were missing. All of them have been restored to match the Japanese original, and the technical claims are the same as in the Japanese version. Read the version before this update (DOI: 10.5281/zenodo.21614441)
First published
Cite this article(DOI: 10.5281/zenodo.21614440)

This article is archived on Zenodo. Below are both the DOI that always resolves to the latest version and the DOI pinned to the version you are reading.

Go Komura (2026). Announcing Our Technical Blog - A Windows / C# / COM Development Blog. KomuraSoft LLC. https://doi.org/10.5281/zenodo.21614440 https://comcomponent.com/en/blog/2026/01/25/000-hello-world/

DOI (latest version)
10.5281/zenodo.21614440
DOI (this version)
10.5281/zenodo.22217102

We have launched the KomuraSoft LLC technical blog. On this blog, we will share insights gained on real Windows application development projects, along with technical information that is useful in day-to-day work.

Who This Blog Is For

We write for readers like these.

  • Windows desktop application developers: you work with WPF, Windows Forms, or the Win32 API on the job, and you sometimes get stuck on a design choice or on isolating a defect
  • People who have inherited existing assets: you are responsible for COM, ActiveX, VB6, VBA, and similar code that runs but is hard to touch
  • In-house system owners: you are the one who decides whether to build in-house or outsource, and whether to keep, wrap, or replace what you already have
Who this blog is forA diagram showing that this blog is written for three kinds of readers - developers who work with WPF, Windows Forms, and the Win32 API on the job, people who have inherited existing assets such as COM and VB6, and in-house system owners who decide questions such as build in-house versus outsource.Desktop application developersThis blogPeople who inherited existing assetsIn-house system ownersDesign choices and triageCOM, VB6, VBAKeep, wrap, or replace

Figure 1: The intended readers are three groups - developers, people who have inherited existing assets, and in-house system owners.

Knowledge map for this article

This article announces the launch of the KomuraSoft LLC technical blog and names three themes it will cover: Windows desktop app development, C#, and COM. Windows desktop app development takes WPF, Windows Forms, and Win32 API as its technical elements, and C# is often assumed as the implementation language. C# runs on the .NET runtime, and interop topics such as calling COM components are covered as well. ActiveX is a technology built on COM, and much of the existing code written in VB6 or VBA also works by calling COM components in a typed way, so engineers who have inherited those assets are included among the intended readers.

Technical blog launch announcementDiagram showing the three main themes the KomuraSoftWeb blog covers, namely Windows desktop app development, C#, and COM, along with their constituent elements WPF, Windows Forms, Win32 API, and .NET, and their relationship to VB6 and VBA as existing assetsusesusesusesusesWindows Desktop App DevelopmentC#COM (Component Object Model)WPFWindows FormsWin32 APIDevelopment tools (Visual Studio/Git/Process Monitor)

In the diagram a solid line marks a relation that always holds and a dashed line marks a conditional one (the conditions are given per relation on the detail page). The full list of relations (4 in total, with evidence and certainty) and the definitions of the main concepts are collected on the knowledge map detail page (in Japanese). Data: JSON-LD / Turtle

What You Get from This Blog

  • Case-based solutions: for problems we actually ran into, we write down how we isolated them and how we fixed them, in a form you can follow step by step
  • Practical decision tables: where the call between two options is hard to make, we lay out the conditions and the choices in a table
  • Pointers to primary sources: we link to the official material an article rests on, such as Microsoft Learn and IPA, Japan’s Information-technology Promotion Agency
What you get from this blogA diagram showing that every article delivers three things - case-based solutions describing how a real problem was isolated and fixed, practical decision tables that lay out conditions and options, and pointers to primary sources that lead to official documentation.Articles on this blogCase-based solutionsPractical decision tablesPointers to primary sourcesIsolation and fix, in a form you can followConditions and options in a tableLinks to official documentation

Figure 2: What you get from an article comes down to three things - case-based solutions, practical decision tables, and pointers to primary sources.

Main Topics We Will Cover

  • Windows application development: WPF, Windows Forms, Win32 API
  • C# / .NET: language features, performance, design patterns
  • COM / ActiveX: integration with and migration of existing systems
  • Development tools: Visual Studio, Git, and other handy tools

If you want a single article to start with for each topic, these are the ones (all published after this post).

Topic Where to start
Windows application development Choosing Between WinForms, WPF, and WinUI - A Practical Decision Table
C# / .NET A Practical Decision Table for C# async/await - Task.Run and ConfigureAwait
COM / ActiveX What Is COM? - Why the Design of Windows COM Is Still Beautiful Today
Migrating existing assets How to Handle ActiveX / OCX Today - A Keep / Wrap / Replace Decision Table
Development tools A Practical Guide to Process Monitor - Pinpointing Settings Not Applied in 10 Minutes

Everything we have published is reachable from the blog index.

Updates

We publish on an irregular schedule, but whenever we have insights or investigation results that are useful in the field, they go up.

There are three ways to follow updates.

How to follow updatesA diagram showing that the publication of a new article can be followed through three channels - subscribing to the RSS and Atom feed, new-post announcements on X, and the GitHub repository holding the sample code.New article publishedRSS / Atom feedAnnouncements on X (Twitter)Sample code on GitHub

Figure 3: Updates reach you through three channels - the feed, X, and GitHub.

About the Author

Go Komura (Representative, KomuraSoft LLC)

Specializes in Windows software development, technical consulting, and defect investigation. Particularly strong on projects that carry existing assets, and on investigating failures whose root cause is hard to see.

Recent articles sharing the same tags. Deepen your understanding with closely related topics.

These topic pages place the article in a broader service and decision context.

This article connects naturally to the following service pages.

Windows App Development

As an entry point to our practical topics spanning Windows development, C# / .NET, and COM, this article naturally leads into a Windows application development consultation.

Author Profile

Profile page for the article author.

Go Komura

Representative of KomuraSoft LLC

Focused on Windows software development, technical consulting, and investigations into failures that are difficult to reproduce.

Back to the Blog