Telerik OpenAccess ORM

The ConfigFile specifies the short filename (no absolute path) of the OpenAccess ORM configuration file you wish to use for the project. In the configuration file you can specify a database connection (e.g. database name, server name, user name and password). For more information about OpenAccess ORM configuration files, refer to Configuration File.

The ConnectionId is the name of the database connection. The parameters of the ConnectionId are specified in the configuration file. For a database create/update the ConnectionId in the Visual Studio is used for creating/updating the database during the post-build step or when you explicitly call the database create/update commands.

The EnhancementOutputLevel sets the amount of information to be printed during enhancement. Default value is "1".

If the value of the Enhancing property is set to "true", the OpenAccess ORM enhancer, is called automatically after the Visual Studio .NET compiler. The OpenAccess ORM enhancer modifies the project assembly to enable transparent loading and storing of member values of persistent instances and registers all persistent classes in the database schema. If the project contains persistent classes, Enhancing should be set to true. If the Enhancing property is set to false, the OpenAccess ORM enhancer will not be called.

The OpenAccess ORM enhancer is described in The OpenAccess ORM Enhancer.

If the value of the UpdateDatabase property is set to "true", it specifies that the database will be updated during a Visual Studio build.

A create or update sql script file will also be created in the assembly output directory (bin\Debug) of your project during Building / Rebuilding your project, if this property is set to "True". The script file name will start with Schema_Creation or Schema_Migration followed by the backend and the timestamp ("Schema_Migration_mssql_2006-04-10_12-41-39.sql").

If it is the first time that you are Building / Rebuilding your project, with the database property set to "True", then another .sql file using the default naming convention, i.e, Database_Creation_Driver_DateTime (for e.g. Database_Creation_mssql_2006-05-31_16-45-46.sql) will also be generated, which will contain the SQL DDL command: CREATE DATABASE DatabaseName (Refer to Schema Generation for more information).

The Policy File specifies the policy action file. This file contains the policy definitions and structure.

The Project File specifies the name of the file that contains build, configuration and other information about the project.

The Project Folder specifies the location of the project file.

If the value of the UseMSBuild property is set to "true", then the MSBuild integration is used instead of the Visual Studio integration. This is useful while using the command-line build environment (Refer to OpenAccess ORM MSBuild Integration for more information).

This property is only applicable for VS2005 projects, since the MSBuild Class is new in .NET 2.0 framework.