> Run the tutorial in PowerBuilder
Make changes for a .NET Web Forms application
Create a .NET Web Forms target and project
Deploy a .NET Web Forms project
Run the application from a Web browser
Tutorial requirements
To run the tutorial application successfully, you must have
configured ASP.NET for a .NET Web Forms project on the system where
you will deploy the application. This includes setting up appropriate
permissions for running SQL Anywhere and connecting to the EAS Demo
DB V125 database as an ASP.NET user. For information on configuring
ASP.NET, see the first chapter in the Deploying Applications
and Components to .NET book.
Before you deploy the PowerBuilder tutorial application as an ASP.NET Web application, make sure the application runs successfully from the PowerBuilder environment on your development system. The complete tutorial application is included in the Tutorial\Solutions directory in the PowerBuilder installation path.
Since you add a Web Forms target to the solutions workspace, it is best to copy the tutorial application workspace and targets to a separate directory first. That is what you do in the first steps of this tutorial.
Create a subdirectory under the My Documents\Sybase\PowerBuilder 12.5\Tutorial
directory and name it Web Forms.
Copy all the files from the Tutorial\Solutions folder to the new Tutorial\Web Forms folder.
Select Programs>Sybase>PowerBuilder 12.5>PowerBuilder 12.5 from the Windows Start menu.
The PowerBuilder development environment displays.
Select Open Workspace from the File menu.
The Open Workspace dialog box displays.
Navigate to the Tutorial\Web Forms folder
that you created in Step 1, select MyWorkspace.pbw,
and click Open.
The workspace containing the pbtutor.pbt PowerScript target file opens in the PowerBuilder IDE. This target contains two library files (pbtutor.pbl and tutor_pb.pbl) with all the objects of the tutorial application.
Click the Run button in the PowerBar.
The Login window displays for the tutorial application.
Enter dba as
the value for the user ID and sql as
the password.
Upon successful login, an MDI frame window with a menu and toolbar displays.
Test available menu options to make sure they are working, then terminate the application.
