The release-defining feature of PowerBuilder 11 is its ability to deploy existing applications as .NET Windows Forms and Web Forms applications and components of business logic, namely custom-class user objects (NVOs), as .NET assemblies and Web Services. Although PowerBuilder's adoption of the .NET Framework represents a great leap forward for application developers, the implications of converting a desktop, client/server application to an ASP.NET Web application are significant. Those of you who have been working with PowerBuilder 11 know this first hand just from the sometimes daunting list of unsupported features that can appear in the Output window after deploying a .NET target (Figure 1).

The unsupported features list contains valuable information necessary for you to successfully bring your application's functionality into the .NET world; however, the organization of that information could stand some improvement.