GenWise project files use the extension .gwapp, the GenWise installer registers GenWise Studio as the default program for this extension.
GenWise .gwapp files are XML files that conform to a specific schema. They can be viewed with any XML viewer, and modified with any XML editor.
Project files contain the following:
 | Basic project information. |
| A complete tree of template instances with all their configured template option values. |
| Custom code that has been added to User Codeblocks. Custom code is stored in the project file and re-attached to the template output on every generation. |
Every GenWise project has one project file that contains all the project settings. Every project has its own directory for generated output, this can be configured on the Project Options Page.
A application created with GenWise may consist of multiple projects. A typical example of this is an ASP.NET web application, which consists of a Database Repository, a BO-Layer project (NHibernate Templates) and an ASP.NET project (ASP.NET 2.0 Templates).
GenWise does not use solution files for organizing multiple projects in a single solution. Project files cause other project files that they depend on to be loaded into GenWise Studio before they are loaded themselves.
For example, when an ASP.NET project is loaded into the empty GenWise Studio environment, it will cause the related BO-Layer project to be loaded first, which will in its turn cause the related Database Repository to be loaded first. So when you open the ASP.NET project, GenWise Studio first loads the Database Repository, then the BO-Layer project, and finally the ASP.NET project.