TSF COM in-proc server

First of all, thank you so much for this repository. I just have a few questions and could use some help. I'm writing a TSF text service, and obviously it requires a COM in-proc server that gets registered with the TSF. I want to keep our projects in C# as much as possible, so I had to find out how to convert a C++ COM in-proc server over into the dotnet world, and I'm glad it was fairly painless.

Since that part is out of the way, I just have a few questions about structure in terms of communication between COM servers. Our in-proc server is inside of a DLL that is loaded by the TSF. I want to communicate with our in-proc server DLL from our main WinUI application. According to the TSF docs, this DLL is mapped into the address space of wherever the TSF is running, and TSF acts as a middleman between applications and text services. Based on this repository, is there a way the COM in-proc server could also act as an out of proc server, or should I create an out-of-proc server on our WinUI application, and have it loaded by the DLL the same way the example loads it via the ROT?

Thank you so much for your time and this example.

The issue asks about architectural design for a TSF text service involving COM in-proc and out-of-proc servers. The repository contains examples of COM interop in .NET. To start, examine the existing examples for server registration and ROT usage. Understanding the TSF documentation and the specific communication requirements between the DLL and WinUI app is necessary. The goal is to determine whether to extend the in-proc server or create a separate out-of-proc server.

由索引模型根据 Issue 内容生成。