This part describes how to create and deploy Web Forms applications.

• PowerBuilder Web Forms Applications
  The PowerBuilder Web Forms solution employs ASP.NET technology. It has a three-tier architecture, with the browser client as the front end, and the PowerBuilder components on the IIS server as the middle tier. The database tier remains unchanged.
• Client-Side Programming
  The use of client-side events can improve application performance because they do not require round trips to the server.
• Permanent User Accounts
  Due to the stateless nature of the HTTP protocol, file and directory operations in a Web application typically do not persist after a user session has ended.
• Managers in Web Forms Applications
  You can enable print, file, mail profile, and theme managers in a Web Forms application.
• Web Forms Properties
  In addition to PowerScript properties that are converted to .NET properties and JavaScript attributes, a .NET Web Forms application has global properties that you can set at design time, and several built-in control properties that are not valid for other types of PowerBuilder targets.
• System Functions for .NET Web Forms
  System functions specific for .NET Web Forms applications allow you to open the various managers for Web Forms applications, obtain global configuration settings, download files for viewing or printing by the application user, and upload files to the Web server.
• Unsupported Features in Web Forms Projects
  When you deploy a PowerBuilder application as a Web Forms application to an IIS server, PowerBuilder lists any unsupported features in the Output window. For the most part, unsupported features fail silently in the Web Forms application, but unexpected results can also occur.