Creating a new OpenEdge project

Progress Developer Studio for OpenEdge provides various project types for OpenEdge application development and also a framework to create custom project types, as required. Facets for each project type is configured by default.

1. Select File > New > OpenEdge project from the Progress Developer Studio for OpenEdge main menu bar or the Project Explorer view context (right-click) menu. The New OpenEdge Project wizard opens and displays the Create an OpenEdge Project page.

2. Enter a name in the Project name field. The root folder for the new project with this name is created in your current workspace. To choose a different location for the project, clear the Use default check box. Then either browse to or enter the path to the required location.

3. Do one of the following:

To create a project for the back-end development of the application, select the Server category from the left section.

Select the server type that you want to deploy the services to and the transport type that you want to use for deploying the application.

To create a project for the front-end development of the application, select the Client category from the left section.

Select the Desktop Application or the Web Application option button to create a project for a desktop application or a web application respectively and select one of the project types.

To create a basic, ABLUnit, Dynamics, or custom OpenEdge project, select the General category from the left section.

Note: If you do not select a category (Client, Server, or General) and click Finish, a basic OpenEdge project without any specialization is created.

4. Click Finish. The project is created and is displayed in the Project Explorer view.

5. To review or modify project properties after the project is created, right-click the project in the Project Explorer view and select Properties.

Note: For large applications with multiple modules, it is recommended that you create separate projects for the modules. You must also create separate projects for modules that have a different PROPATH or that require different database connections.