You can configure ASP.NET for a smart client project
before or after you deploy the project to an IIS 5.0 or later server.

All files and directories that you access from a
smart client application on a Web server must have
appropriate ASPNET (IIS 5.0), IIS_WPG (IIS 6.0), or IIS_IUSRS (IIS 7.0 and 7.5) user
permissions.

For an example of granting user permissions to a directory, see Setting Up a SQL Anywhere Database Connection.

When you deploy directly to a remote computer, system information about the deployment computer, including its OS and IIS versions, is passed to PowerBuilder through the Windows Management Instrumentation (WMI) interface. Deployment through the WMI interface requires administrator privileges. If you make any changes to administrator accounts on a remote computer, you will probably need to reboot that computer before you can deploy a .NET Web project from PowerBuilder.

If you deploy to an MSI setup file, and run the setup file on a deployment computer, PowerBuilder can use the Windows API to obtain information about the OS and IIS versions on that computer.

• IIS Installation
  You can install IIS from the Control Panel, but you might need a Windows operating system CD.
• Selecting the Default ASP.NET Version
  If you installed multiple versions of the .NET Framework on the target Web server, you should make sure that IIS uses a supported version for PowerBuilder .NET applications.
• Setting Up a SQL Anywhere Database Connection
  Full control permissions are required for directories containing databases that you need to access from your .NET Web Service applications.
• Configuration Requirements for Windows Vista and Later
  When you run PowerBuilder on Windows Vista or Windows 7 under a standard user account, and attempt to deploy Web Service projects, the User Account Control (UAC) dialog box appears. This dialog box allows you to elevate your privileges for the purpose of deployment.