Forum Discussion

jkrolczy's avatar
jkrolczy
Regular Contributor
6 years ago

Opening TestComplete from .pjs file Defaults to x64 version - x86 version wanted instead

All,

 

When TestComplete 32bit(x86) existed ONLY,  a .pjs file extension used this as a default when opening TestComplete.

 

With the introduction of 32bit(x86) and 64bit(x64) TestComplete versions, opening TestComplete from a .pjs file extension defaults to the 64bit version of TestComplete.   I am still interested in the 32 bit use.

 

Currently, I have to open TestComplete x86 version first and then open the desired project.

 

It is not possible to reconfigure the .pjs to open to the 32bit TestComplete by Default from what Windows does

with for editting what .pjs file extension would use.  It does not take the change.

 

Is this something that can be fixed in future releases of TestComplete ?

 

For those interested in how to change,

 

Work-around to change how a .pjs file extension opens TestComplete is:

 

1)  Close TestComplete

 

2)  Find the 64bit version of TestComplete.

 

     C:\Program Files (x86)\SmartBear\TestComplete 12\x64\Bin

     rename TestComplete.exe

         i.e.   TestComplete64.exe

 

3)  Find a .pjs file and dbl-click to open TestComplete.

 

      Win7 will provide you a pop-up asking what to open with.

      Win10 - I don;t have those steps yet.

 

      Here you can confire the .pjs file extension to use a default path to 32bit version:

        C:\Program Files (x86)\SmartBear\TestComplete 12\Bin\TestComplete.exe

      

      Browse and set path to use 32bit version of TestComplete if you are wanting to change this behaviour.

 

      Apply change.

 

3)  TestComplete should now open to 32bit version from a .pjs file extension.

 

4)   Find the 64bit version of TestComplete and rename back:

 

     C:\Program Files (x86)\SmartBear\TestComplete 12\x64\Bin

     rename TestComplete64.exe  back to TestComplete64.exe

 

 

 

5 Replies

Sort By
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    6 years ago

    Basically, this is a windows registry thing.  Not sure exactly where it is but it is "associated applications".  Basically, the PJS file is associated in the registry with the x64 version.  Change that registry, and you're all good.

    • jkrolczy's avatar
      jkrolczy
      Regular Contributor
      6 years ago

      agree there is a Win reg spot somewhere for .pjs to change
      have not found yet or it may be encrypted ?

  • cunderw's avatar
    cunderw
    Community Hero
    6 years ago

    You can just right click and select Open With, no need to rename the EXEs

    • karkadil's avatar
      karkadil
      Valued Contributor
      6 years ago

      Carson is right, there is a simpler solution:

      1. Right-click PJS file with pressed SHIFT button
      2. Select Open with...
      3. More options, then scroll down, then Look for another app

      This is for Windows 8.1, I suppose that for Windows 10 steps will be similar

      • jkrolczy's avatar
        jkrolczy
        Regular Contributor
        6 years ago

        All,

        I agree with all the approaches and actually tired these.

        What I think is the issue here is that because the file name is the same -  TestComplete.exe

        exists in 2 locations - throws off the Open With approach.  Going through those steps does not

        change anything and TestComplete x64 still opens from a .pjs file.

         

        For me renaming the x64 TestComplete.exe breaks the file ext. for .pjs and allows me to reset it to where I do want it to point using the Open With approach.

         

        Thanks to all for your replys back.

        JamesK