When performing development work, customizations, or configuration to an application project, the development and unit testing is normally performed in the Agentry Development Environment. This includes the Agentry Development Server to which the application will be published, and the Agentry Test Environment, used for development and other testing of client functionality. When publishing to a Development Server, the publish performed is a development publish. A development publish should only be performed to an Agentry Development Server.
A development publish will transfer the definition files in the application project from the Agentry Editor to the Agentry Development Server. The files are stored on the file system at the installation location of the Server in the sub-directory Application\Development. A development server has no concept of application versions. When a development publish is performed, the previous version of the application on the Server is overwritten.
In a development publish, SQL scripts, file system scripts or batch files are written to the file system as separate, editable files. This allows for modification to these synchronization components on the Server without the need for a publish. Any other application modifications made require a publish to the Server to be available to the Agentry Clients or Agentry Test Environment.
The options for a development publish are limited to selecting the Agentry Development Server to which the application will be published, and whether or not to create the localization base files. Delayed deployment and version information cannot be set.
The main reasons for performing a development publish are to perform development and unit testing of an application during the development process. Additional testing should also be performed in a Production environment established for the purpose of quality assurance and user acceptance testing.