Forum Discussion

jrussell2's avatar
jrussell2
New Contributor
11 years ago

Test Execute does not load 32-bit DLL?

Using TestComplete/Test Execute 9, on aWindows 7 64-bit OS. I'm calling an external DLL that is 32-bit.   I followed the steps to define the environment:   Def_Environment := DLL.DefineEnvironmen...
colinstrydom's avatar
colinstrydom
Occasional Contributor
11 years ago

I build my own dlls and use some windows dlls in my projects and but I don't use it the same way as you.

 

I add my dll's to the CLR Bridg of my project and then just call them from script. When adding custom dlls, you just need to ensure they are on the target machine, and you can use relateive paths as well.

 

I then perform the call in C# script as follows

 

dotNET["FileCompare"]["LineComparison"]["zctor"]["comparefile"](lreferencefilePath,lreferenceFileName,linputFilePath,linputFileName,loutputFilePath,loutputFileName,ldeleteOldLogs)

 

This works on the latest test exectute, I cannot confirm on version 9

mes6073's avatar
mes6073
Contributor
11 years ago

We also use the CLR Bridge to access DLLs, first in v9.0 and currently 10.6 of both TestComplete and TestExecuteand. I will say that we did have issues with older C++ DLLs, but our newer, custom DLLs based on .NET 3.5, 4.0, and 4.5 frameworks worked fine with the CLR Bridge in a distributed test model, but I recently also ran that with just TestExecute hacnling both master and slave roles .