10 Reasons to Use PAServer for Remote Windows Deployment


Everyone knows PAServer (Platform Assist Server) is the easy way to deploy and debug multi device apps from Windows to Apple OS X and iOS. It handles all the bundling and deployment from your Windows development platform across the network, via a virtual machine, or even to the cloud.
Previously I showed you how to connect to a Android Emulator on another machine (or outside your VM), but did you know you can also use the PAServer to deploy and debug against a remote Windows machine? It isn’t required, so isn’t as immediately obvious, but it is supported and pretty easy to setup.
If you are already developing on a Windows machine, why us PAServer to test against a remote Windows machine? There are a lot of reasons, here are a few . . .

Testing on machine without IDE installed
Windows tablets
Different CPU architectures (64-bit vs 32-bit)
Different numbers of cores
Utilizing specialized hardware
Running outside / inside a virtual machine
Deployment on a server (remote, local, in the cloud)
Debugging on more than one version of Windows
Debugging issue that only occurs on one machine
Bundled deployment options

Now that we see the need, how do we do it?
Install PAServer on the target computer. You can find it at C:Program Files (x86)EmbarcaderoStudio17.0PAServer if you used the default install location during your original install. When installing PAServer, you either need to use a different install location (to a user writable folder), or specify a custom scratch-directory, as the default is not writable (unless you run PAServer as Administrator) and will give you an E0009 PAClient Error.

Use the Connection Profile Manager to create a new Windows profile.

Instead of the default of OS X, choose either Windows 32-bit or 64-bit. The rest of the configuration is the same.

Then form the Project Manager, right-click on the Windows platform you want to deploy remotely, and select properties.

And then select the new connection you want.

This works with any project type (FireMonkey, VCL, Console, etc.)

Now you can also use the Deployment Manager for Windows apps as well.

Comments are closed.