Test DLL not found?
Hi, I'm testing TestComplete and I'm trying to use some of our existing .NET DLLs. I added the DLL into the CLR Bridge configuration parameters and I am using it through the dotNET. obje...
Forum Discussion
HKosova
Alumni
AlumniHi Pascal,
The issue is caused by the specifics of the .NET runtime's assembly resolving procedure. Since the dotNET calls are performed in the context of tcHostingProcess.exe, .NET considers it the "main" application and therefore looks for dependent assemblies in its folder. That's why, placing the assembly next to tcHostingProcess.exe solves the problem.
To avoid copying the assemblies to the TestComplete folder, I recommend that you put them to the GAC instead.
The issue is caused by the specifics of the .NET runtime's assembly resolving procedure. Since the dotNET calls are performed in the context of tcHostingProcess.exe, .NET considers it the "main" application and therefore looks for dependent assemblies in its folder. That's why, placing the assembly next to tcHostingProcess.exe solves the problem.
To avoid copying the assemblies to the TestComplete folder, I recommend that you put them to the GAC instead.