An ASP.Net Web Application (Terminal Screen Appearance) uses Web Forms and is intended for users who will access your application by running a standard Web browser, typically from a desktop or laptop computer.
Refer to Choosing Web Forms or MVC for more information on Web Forms
This particular project type is designed for use in the following cases:
The data source type is MCP T27.
The data source type is OS 2200 UTS.
The data source type is MCP COBOL and you imported SDF forms.
The data source type is OS 2200 TIP and you imported DPS forms.
This project type ignores the Label property associated with each field of the client message. Instead of using labels from the client message, the static text that you captured, or imported from your terminal screens or forms, is preserved on the generated Web pages.
You can, optionally, discard the static text from your original application and redesign the interface with your own labels. For this case, refer to Creating an ASP .Net Web Application.
Procedure 1 - Adding the ePortal Presentation Project
In Solution Explorer, right-click the solution node, click Add, click New Project....
In the Create a new project dialog box, do the following:
Notes:
Select C# or All Languages from the Language list.
Select Windows or All Platforms from the Platform list.
The ePortal templates are not displayed if other values are selected.
Select ePortal Previous Versions from the Project Type list.
The ePortal Previous Versions templates are displayed.
Do any one of the following to select the template:
From the templates, select ASP.Net Web Application (Terminal Screen Appearance), and then click Next.
Enter ASP.Net Web Application (Terminal Screen Appearance) in the search option, select the template from the search result, and then click Next.
Optionally, change the Project name, Location, and Framework, and click Create.
Notes:
If you do not select a desired Framework, a default Framework version is selected.
For information on selecting the .NET version, refer to Multi-Targeting Issues.
If a master page should be applied when generating new .aspx pages, select UseMasterPages and set the value to True on the Presentation Generation Options dialog. Refer to Modifying the Master Page for information on master pages.
Review the remaining property values. These values dictate the behavior of the Web pages when they are created.
Make any necessary changes on the Presentation Generation Options dialog; refer to Presentation Generation Properties for a Web Browser Project for information about the properties.
Click OK. The presentation project appears in Solution Explorer.
Procedure 2 – Controlling the Look and Feel
Once you have created your presentation project, you can control the look and feel of your Web pages. Review the topics at Controlling the Look and Feel of Your Presentation.
Building the Solution
Note: Before building your solution, review the topics at Controlling the Look and Feel of Your Presentation. Some of these steps are best performed before you build your presentation project and some steps cannot be completed until after you have built your presentation project.
To build your solution, in Solution Explorer, right-click the solution node, and then click Build Solution. The presentation project is populated with appropriate items. Refer to Building Your ePortal Solutionfor more information.
Procedure 3 - Controlling the Behavior
Once you have built your presentation project, you can control the runtime behavior of your application. Refer to Controlling the Runtime Behavior of Your Presentation for more information.
Procedure 4 - Testing
Refer to Testing a Presentation Project
Next Step