Running and debugging an application on a remote machine is identical in almost every respect to using your local machine. You can use the three menu items Application > Start, Application > Debug and Application > Interact to launch the application in the normal way. The only difference is that for remote startup you must specify a remote machine in the project's debug settings.
In the "Remote machine" section, an option box displays the name of the machine on which the project's application is to be run. By default, the selection will be the local machine. Before you can select a remote machine, you must first establish a debugging connection.
If the connection is successful, the newly connected machine is added to those listed in the "Remote machine" option box. You can now select this machine.
If the connection does not succeed, you should ensure that you have successfully started the debug server program on the remote machine. (See "Starting the debugging server" above.)
Having selected a remote machine, you must also ensure that Functional Developer can locate the program (EXE or DLL) on the filesystem of the remote machine.
\\spiral\c_drive\apps\reversi\release\reversi.exe
spiral is a machine name, and c_drive is the share name of the drive containing the program release folder.
You are now ready to run and debug the application remotely. Application > Start starts your application running on the remote machine. All the usual debugging and interaction facilities will now be available.
Details about the connection to a remote machine are stored and saved with the project. Functional Developer tries to re-establish the remote connection automatically when you next open and try to run the project.