The CLR Bridge interface in TestComplete is not meant to test assemblies/DLL's but to use such assemblies and DLL's to be able to test other applications. The assumption is that such things are staticly present when test complete attempts to access them.
As far as I am aware, there's not a neat way to reload the assembly programmatically.
Well, I am not really testing the assembly I am just trying to use some features from it in my scripts so I don't have to re-write code that already does what I want it to. The problem I have is that after I close all threads the next go around If I want to re run the script it won't it won't work because TestComplete still holds the old reference in memory and only releases them when I close it. It would be a nice feature to have to be able to do this. Anyways, thanks for your reply.
Hi,
> If I want to re run the script it won't it won't work
Can you provide more details about what actually does not work? Test cannot be started, or some error is posted to test log or something else? Screenshot(s) and/or exact error message might help as well.
Hello,
yes, it would be great, if TestComplete could release the assembly as soon as it is not in use!
I use a .NET assembly to read test configuration values using entity framework. During development I always need to
Is this easier than restarting TestComplete? I'm not sure.. Both approaches are definitely uncomfortable.
Bernd
