Personally I don't, but my interest is to write in c#, can't stand the millions of files and long compiles of C++. Plus I like the dotnet library, linq, etc.
I tried wrapping the MQ2Main in various ways, for C++CLI or suchllike, or even just pinvoke. Tried running up dotnet appdomain. I keep getting errors on clr initialize, or with straight pinvoke I can get data (strings etc), from MQ2, but when I try and write back it always bombs EQ process (ie, I can see incoming chat in a c# plugin, and react to it, but I can't even write an echo string back out, so I can't DoActions or anything.
I would have re-written the dotnet plugins that used to be around (but using the latest CLR, they all seemed to be v1), but as I say, can't get the CLR to initialize. It gives some non helpful errror. Roslyn would be really good to allow any dotnet language as a script.
I can handle all the appdomain stuff to allow plugin unload/reload etc, and script compilation on the fly, but only from C#.
My overall goal was to write a quest automater, with a separate UI which you could describe steps of a quest in, describe how to tell the step was achieved, and give actions to complete each step. Group sync, group member role allocation, so one could be indicated as the puller and do different actions, and so on. Then folks could provide their own quest scripts, written in any dotnet language. Examples would be similar to the HA scripts people have around but with a basic set of functionality as the baseline. A shim for MQ2 would communicate back and forth to allow overall status updates to the "controller" and to initiate commands in EQ.
But no way in hell I want to write that in C++ and the macro language is even worse.
Erm, also I was intending to be running MQ2 also, for the baseline functions and plugin stuff it provides.
