Forum Discussion

Philip_Baird's avatar
Philip_Baird
Community Expert
11 years ago

Discrepencies around COM Object registration

Hi, I am currently writing a C# Library to manage Test Execution using the Test Execute COM Object and I have a concern on the COM registeration.   I have both Test Complete and Test Execut...
  • TanyaYatskovska's avatar
    TanyaYatskovska
    11 years ago


    Hi Phil,


     


    There is no TestExecute library. You need to add the TestComplete library which refers to TestExecute, like it's listed in the article.


    We will correct the information in our documentation.


     




hlalumiere's avatar
hlalumiere
Regular Contributor
11 years ago
You do not need to worry about COM registration at all to be honest, unless your installation was damaged. To get the reference to TestComplete or TestExecute, reference the .exe. Visual studio will generate an Interop DLL when you build. Copy that DLL to the output, and then reference it instead of the exe from your app. Now you can develop your app on any machine no matter if it has TestComplete installed or not. When you actually instanciate check for an exception when creating the TestComplete.Application object. You can trap if something is wrong at runtime.



In VB you could also use late binding to abstract it all away. But C# doesn't support late binding pre-4.0. In 4.0+ you can use late binding with the poorly-named "dynamic" keyword. (I say poorly named because both c# and vb are static languages, there is no dynamic typing...)