AutoHotkey Community

Начиная с версии .NET 2.0 достаточно указать в экспортируемых методах директиву
.export [<ordinal>] as <export_name>
или
.export [<ordinal>]
все остальное компилятор сделает сам. Не правда ли легко?
К тому же, это позволяет без изменений компилировать исходный текст как под x32, так и под x64.

Вот первоисточник
http://qinjunit.googlepages.com/NET.2.0.IL.Assembler.pdf

The good news is that version 2.0 of the IL assembler does not require these directives at
all, as long as the v-table and VTFixup table are used for unmanaged exports only. Just specify
the .export directives in the methods you want to export to the unmanaged world, and the
flags, the v-table, and its fixups will be generated automatically by the compiler, with the slot
size adjusted for the target platform:

.assembly extern mscorlib { auto }
.assembly YDD { }
.module YDD.dll
.method public static void Yabba()
{
.export [1]
ldstr "Yabba"
call void [mscorlib]System.Console::WriteLine(string)
ret
}
.method public static void Dabba()
{
.export [2]
ldstr "Dabba"
call void [mscorlib]System.Console::WriteLine(string)
ret
}
.method public static void Doo()
{
.export [3]
ldstr "Doo!"
call void [mscorlib]System.Console::WriteLine(string)
ret
}[url][/url]

I tried this process starting from the example and everything worked fine.

However, as soon as I invoke a method from a custom referenced (additional) DLL, the DllCall() fails, returning ErrorLevel 0xe0434f4d, LastError 2.

Do I need to do something special to utilize additionally referenced DLLs (not directly accessed by AHK)?

AHK:


Call chains:
aQuery.ahk DllCall() -> aQueryWrapper.dll\echo()
aQuery.ahk DllCall() -> aQueryWrapper.dll\query() -> aQueryLib.QueryGameServer()

The call to echo() is verbatim copied from the sample code in the first post. The call to query() uses an identical type signature as echo().

The call to echo() works perfectly (ErrorLevel=0). As soon as I hit the call in query() to the additional referenced DLL I get the failure. If I remove everything from the function that references this DLL, it executes fine.

The weird thing is I have written a C# console test app, and calling query() from there, with the exact same arguments, works fine there. In fact I went so far as to hardcode default arguments into the beginning of query(), thus ignoring passed arguments entirely. The console app continues to work and DllCall() continues to fail.

Also, the download links in the original post are turning up empty pages for me (many of Titan's scripts are).

@joelpt
OK. Have you already send him a "C'mon boy, don't do that to me! " - PM ??

Have you tried manually loading the dll so DllCall doesn't automatically try to unload it? It's occasionally necessary for native dlls; I think individual .NET assemblies can't be unloaded anyway, so it probably won't help in this case.

If you don't have any luck with that, you might like to try .NET Framework Interop.

That did the trick, thanks. In fact that turned out to be better suited to my needs (lots of calls into DLL code on a fast timer).