Before distributing DLLs you want to make sure DLL functions are working as they intended.
In order to ensure everything as intended, you want to run your DLL project or debug with Doit. The main purpose of running a DLL project is for debugging. You run DLL project as you would run any other project: set it to current active project and then select from the Run menu the Start command.
Typically you will create a procedure that will contain calls to DLL exported functions for testing. You can call the procedure in System or Drivers' events.
You can trace and step into the exported functions, place breakpoints, and use trace and print statements.
Another way to test is to create a program containing some test/task that calls DLL Export functions. And run the program. Note that during build DLL, the (startup) program is not be called when compiled to the DLL. It will only be called when running from the IDE.
Finally, you can simply add testing code to the events below:
OnInit
OnInitSystem
OnEndSystem
OnEnd
In that events you can call your testing procedures or its exported procedures or IO Tables.
Instead of running, you can use DoIt to debug.
After debugging the DLL project, now it is time to test further by building DLL and use it from other ATEasy projects.
Select Build, Build which will create a ATEasy DLL. Note that even you have a program in the DLL project, it will not affect the DLL generated. The DLL will only exports procedures and IO tables of system and drivers.
After DLL is created, you can switch to other ATEasy project and select a module's (program, system, or driver) libraries' submodule. Insert DLL into the submodule Libraries. (Please see Using ATEasy DLLs for details of inserting DLL). Now ready to test those exported functions.
Call the exported functions, check the input and output parameters and make sure your DLL is working. ATEasy debugger will not allow you to trace/step inside the DLL code. However you can use print or trace messages, MsgBox and other ways to debug your code.