mpduda
It's been tricky but interesting. VST plugins are basically packaged as DLL files of Windows COM(-ish) objects. Despite primarily being a Windows dev myself, I never worked directly with COM libraries or objects before. My app is written in C#, and .NET does have built-in "COM Interop" support, so it is possible. A few years ago, .NET added a new COM Interop Source Generator system [2, 3], and I'm trying to get it working with that. So far I've been making some progress, but it's still a lot of tedious work to setup.
(There are libraries/packages out there that implement VST in .NET already, but they mostly focus on plugin creation while I only need hosting. They're a lot heavier and more capable than I need. They also didn't use the newer Source Generator approach, so I figured I'd give it a shot myself.)
2. https://learn.microsoft.com/en-us/dotnet/standard/native-int...
One issue I noticed with my project [1] is that the description is for the wrong thing. This is probably partially my fault, since I wrote about two projects in one comment [2]. The music production app is closed source, but the UI library I maintain for it is open source. Seems like that might have thrown off your AI tool.
It's built using C# and WPF, and a related project I work on is an open source MVVM framework called UpbeatUI for making WPF apps that behave vaguely like mobile apps. It's for apps that have a main bottom layer and modal popups that float above and can be closed by clicking/touching the background. Pulselyre uses UpbeatUI, and I actually originally extracted UpbeatUI from a much older version of Pulselyre.