Alright, time for an update. We are certain that the issue is related to our app's interaction with the DLLs since we can take the DLLs out and everything else works fine. What's strange is that our app runs flawlessly from SED and WED, but crashes in a built project (and yes, I've made sure that the dlls are copied into the build folder). Even stranger- I noticed that if I didn't kill the app immediately when it crashes, the program actually continues without a problem, even utilizing functions from the DLL. Unfortunately I don't know any way to suppress the crash dialogue, and if you close the dialogue box, the whole app goes away. Our DLL actually references a third DLL. At one point, it seemed like the executable would crash because of the third DLL (since it looks like A7 tries to open any dll in the exe folder, and crashes if it is unsuccessful), so we moved it to a subfolder and changed the way we referenced it in our DLL. That got rid of the invalid memory read error, but the build still crashes immediately on running. We're pretty baffled.

@EvilSOB for sure we've had published builds that worked with our dlls. I did numerous published testing trials at various stages. What's frustrating, is I can't even seem to get back to any working version. I have backups through last September, but none of them work anymore.

I've tried reinstalling A7.

Out of curiosity, what does SED do differently from the built exe?


Ok- a lot has happened since I began to write this post. My boss stepped in to help me out and he discovered some very odd behaviour:
-On my computer, the built version finds the dll, but causes a crash with unhelpful dialogue (though the program continues to run correctly, including utilization of the dll)
-On my bosses computer, the same build works without issue.
-On a third computer, the app can't even detect the dll

This is very strange indeed.

Currently, we are trying to rewrite our dll in lite-c with LoadLibrary. I'm still interested in why what runs in SED is different from what is built into the exe.

Thanks for reading!