Scenario 2: Using remote IIS as the .NET server

In Guide 1, you have successfully deployed and run the installable cloud app in the local development environment (using IIS as the web server for hosing the client app files and using the built-in Kestrel as the .NET server for hosting the PowerServer Web APIs).

And in scenario 1 in Guide 2, you have successfully configured the local IIS as the .NET server and run PowerServer Web APIs on IIS.

Now, you might want to deploy both your client app files and the PowerServer Web APIs to the remote IIS server. This guide will show you how to transfer your client app from the local environment to the remote server. This guide will set up a remote IIS server and use it as the Web server (hosting the client app) and the .NET server (hosting the PowerServer Web APIs).

This guide will reuse the PowerServer project object salesdemo_cloud used in Guide 1. Make sure you have followed the instructions in Guide 1 > Minimal efforts: Deploying the sample PowerServer project to modify and deploy the project successfully.