Strange DLL issue
Is there a way to force TestComplete to release a DLL I have loaded and clear it from memory? I have a DLL I use in my testing. This DLL was created by our programming department to get informati...
Forum Discussion
A little more information.
What really confuses is that I use completely different variables names and lybrary type for the DLL when I load it and define the functions. There are no duplicated references between the two DLLs. The DLLs live in different folders and I define them and load them completely independent of the other. But, I guess since the DLLs are techincally the same file that when it gets loaded to memory it knows this and treats them the same??
joseph_michaud
Staff
StaffAre you using the DLL object in TestComplete to load the DLL? If so, perhaps the ClearSettingsBeforeEachRun property in the IDLLAccessProcessOptions Object Properties may help.
You could also try experimenting with the process Refresh() and RefreshMappingInfo() methods in the faint hope that they can in some way cause the DLL change to be noticed.
Or you may want try renaming one of your DLLs. Hopefully TestComplete will consider them as two separate DLLs. Searching on "windows rename DLL" brought me to various pages describing the use of DUMPBIN, and finally
https://support.microsoft.com/en-us/kb/131313 "How to Create 32-bit Import Libraries Without .OBJS or Source"