There should be only one instance of PHPRunner

This is not exactly correct. Pretty often I open two PHPRunner projects to compare them side by side.
You are correct saying that opening the same PHPRunner project in two instances of PHPRunner is not recommended.

I use 2 open PHPRunner's often to copy code, events or features from other projects.
I found the following however:
If I have a project open and then open another (same instance), the files from the previous project (Eg. a Real Estate Template project) is also uploaded with that project when the second is built and uploaded.
Eg. The pictures of the houses that are part of the Real Estate project is loaded with the built files of the next project, eventhough it's not part of the newer one.
I've tried to get used to closing PHPRunner, then open it again before choosing the next project. This is not a major issue, but can lead to loading files not needed.
Have a great day!

Ralph,

I find it a good thing that PHPR installs a newer version without deleting the last. This allows you to use the newer (less tested version) and use the old as a fall-back. I always open the version of PHPR I want to use and then open the file from inside the application. I am in the habit of looking at the title bar and seeing what version and what build I am using.

If you run into application bugs, the PHPR support is without peer.
/john

There should be only one instance of the PHPRunner application program open under Windows. Unfortunately it's very easy to accidentally get more than one instance going, without even realizing it's happening. This problem occurs if you click a PHPRunner document icon (.phpr file) while PHPRunner is already active.