Make FlexASIO easier to test

[dechamps]

Currently, the only way to test FlexASIO is to load it inside an ASIO host application. This is not quick nor automatable.

One approach would be to build a small .exe that simply makes a series of ASIO calls just like a normal ASIO host application would, maybe even try to transfer a few buffers (e.g. one buffer of silence), and then exits. Even simpler could be to add a rundll32 entry point on the FlexASIO DLL itself to do this.

Maybe this could be done by going through the ASIO SDK for host applications, thus closely simulating what a real application would do. The main downside is that it will probably only work for the currently installed system-wide FlexASIO DLL, not for any DLL that one might want to test against (e.g. the one Visual Studio just built).

[josephernest]

One possibility: could FlexASIO (i.e. "C:\Program Files\FlexASIO\FlexASIO_x...dll") write log to "C:\Program Files\FlexASIO\log.txt"?

This would allow debugging without using WinDbg.

[dechamps]

That would not be wise, as it would cause permission issues due to UAC. That's not the correct place from a technical perspective, anyway. I was thinking of dumping the log to the user directory, e.g. c:\users\your name\FlexASIO.log or something like that.

(I think you meant to post your suggestion in #5, by the way.)