Back to Concepts and HOW TOs

Contents 1 Description 1.1 TypeLib 1.2 AppProject 1.3 WSDL 1.4 StyleProject 1.5 ResourceProject 1.6 SQL Project 2 See Also 3 Tags

[edit] Description

In Bungee Builder, a solution is the top level container for your application. To begin creating an application, you first create a solution, then add projects  to your solution. In every solution there are many different types of projects you can use to perform specific tasks and keep your solution organized. There is no limit to the number of projects you can place in a solution.

While every developer will use project types in the way that best fits their individual projects and development styles, there are specific uses and best practices for each of the project types you’ll find in Bungee Builder. Basic use definitions for each of the project types are given below.

[edit] TypeLib

• Serves as containers for classes. You develop most of your application logic within TypeLibs.
• Contains your Model code
• Serves as the container for the interfaces you create yourself (as opposed to using system provided interfaces)

[edit] AppProject

• Serves as a container for the pages that provide the front end to your final web application
• Provides a way to create a process only application (an option you can choose when adding an AppProject)
• AppProjects are the only project that can be deployed to end users after Posting
• You can add many AppProjects to a Solution, and you may add an AppProject at any time during development

Use AppProjects to package your final functionality into an application ready for deployment.

[edit] WSDL

• Serves as the container of imported [Concept : Understanding WSDL Files|[WSDL files]]

The ability to bring WSDL descriptions of Web services directly into your solution as a project is at the heart of the power of Bungee Builder. You can import as many different services into your solution as needed to complete your application. Further, you can add objects directly to the WSDL project to incrementally add functionality to the service itself at the Bungee layer.

Related Tutorial: Integrate SOAP/WSDL-based Web APIs

[edit] StyleProject

• Serves as the container of one or many custom styles that can be applied to forms

Style projects are used to hold the various style settings that can be applied to forms to give your application a consistent, attractive look and feel. For more information, see Understanding StyleProjects.

[edit] ResourceProject

• Serves as the container of image resources for use in your applications

Keep all your images organized and easily accessible directly inside of your solution. Using WebDav, you can bring images directly from your local machine’s folders and use them as objects in your application. Use multiple resource projects to effectively manage different image sets. For more information, see the following:

• Working with Images
• Uploading a Resource
• Using Images in an Application
• Using HTML Resources in an Application

[edit] SQL Project

• Allows you to choose between creating a MySQL, PostgresSQL, or a Sandbox (MySQL) database project
• For more information on working with this project type, see Introduction to Working with SQL Databases

[edit] See Also

Creating a Solution
Adding a Project to a Solution
Moving a Project to a Different DesignGroup
Working with Images

[edit] Tags