AutoIt's Support for .NET Core created COM objects

[reeset]

Hi, 

I'm going to preface this by saying that I'm not a big AutoIt user myself, but I work in a space (academic libraries) where AutoIt is pretty common.  This is why I'm hoping someone here might be able to help me with a question.  I write some software that a lot of libraries utilize for data management and the software is written in .NET.  To allow users to build workflows beyond what the program provides -- I expose most functions via a shared COM library.

Previously, when the program was written using the .NET framework -- objects created by the application worked fine with AutoIt.  However, I've since transitioned the program to using .NET Core (version 6 currently, version 8 after the first of the year).  .NET Core made some very specific changes related to how they support the creation of COM objects, and I've noticed that while tools can utilize the objects that are created (like powershell, vbscript, vba (in office apps), ActivePerl) -- AutoIT isn't able to see the objects.  I've see this happen with some other scripted languages like AutoIt, and I'm a bit at a loss.  

I've broken down an object to a simple example using the sample Microsoft provides via GitHub -- and I'm able to consume the object in a lot of different programs and languages -- but AutoIt still has issues.  So, given my limited familiarity with the tool, I wanted to reach out and see if anyone that maybe works with .NET Core and AutoIt might have some suggestions -- assuming the two can actually work.  Otherwise, I'm considering writing a C++ host for the library and hoping that solves my problem.

Thanks,

--tr