Configuring Manifests on Windows 8 and Later Operating Systems

Your COM client application from which you control TestComplete:

• Must be digitally signed. (See below.)

• Must be in the Program Files, Program Files (x86) or Windows\System32 folder.

Set the extended privilege level for TestComplete and your COM client application from which you will control TestComplete:

1. Launch a text editor as Administrator.

2. In the text editor, open the manifest file corresponding to the TestComplete version you use:

   • 32-bit version: <TestComplete>\Bin\TestComplete.exe.manifest

   • 64-bit version: <TestComplete>\x64\Bin\TestComplete.exe.manifest

3. Find the requestExecutionLevel element and add the uiAccess="true" attribute to it:

   XML

   XML

     <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
       <security>
         <requestedPrivileges>
           <requestedExecutionLevel level="asInvoker" uiAccess="true"/>
         </requestedPrivileges>
       </security>
     </trustInfo>

4. Save the changes.

5. In the same way, change the manifest of your COM client application.

   Note:

   A manifest may be embedded into the application. This manifest takes priority over an external manifest on Windows Server 2003, Windows Vista, and later Windows versions. On Windows XP, the external manifest has higher priority. If you have trouble connecting to your application, make sure you edited the correct manifest.

Your COM client from which you will control TestComplete must be signed. The easiest way to sign an application is to use signing utilities shipped with Visual Studio or Windows SDK:

1. Use the MakeCert utility to create a self-signed certificate and a private key:

   MakeCert -r -n CertificateName -ss CertificateStore -sr localmachine -sv PrivateKeyFile.pvk OutputCertificateFile.cer

   Where:

   CertificateName - is the name of your certificate, it must comply with the X.500 standard and match the Publisher value in your client application’s manifest. For example, "CN=MyCompany";

   CertificateStore - is the name of your certificate store that will store the generated certificate;

   PrivateKeyFile.pvk - is the name of the file to which the utility will store the private key;

   OutputCertificateFile.cer - is the name of the file, to which the utility will store the certificate.

   The utility will ask you for a password for the private key. Specify the password if needed.

   The utility will generate a self-signed certificate and save it to the specified certificate store. It will also export the private key and the certificate information to the specified .pvk and .cer files.

2. Add the generated certificate to the Trusted Root Certification Authorities store for a local computer. To do this, you can use the CertMgr utility:

   CertMgr /add OutputCertificateFire.cer /s /r localmachine root

3. Use the Pvk2Pfx utility to copy the private key and the certificate information to a Personal Information Exchange file (.pfx):

   Pvk2Pfx /pvk PrivateKeyFile.pvk /spc OutputCertificateFile.cer /pfx OutoutCertificate.pfx

   The utility will generate the .pfx file with the specified name.

4. Use the SignTool utility to sign your COM client:

   SignTool sign /f OutoutCertificate.pfx MyCOMClient.exe

To verify that your client application is signed properly, you can use the verify command of the SignTool:

To learn more about code signing, see the Using SignTool to Sign a File article in the MSDN Library.