Telerik OpenAccess ORM

Telerik OpenAccess ORM Send comments on this topic.
Output and Task List Window
Programmers > Development Environment > Integrating With Microsoft Visual Studio .NET > Output and Task List Window

Glossary Item Box

Any warnings and errors that the OpenAccess ORM enhancer produces are reported to the Output window and to the Task List within Visual Studio. The OpenAccess ORM enhancer runs only if the .NET compiler completes without errors.

The Output Window

All OpenAccess ORM warnings and errors are reported to the Output window (in the Build pane). If the Enhancing project property (see above) for the project is true, the following output appears in the Build pane for a successful OpenAccess ORM build:

OpenAccess ORM post build step: OpenAccess ORM enhancement process... Enhancing Assembly... OpenAccess ORM: enhancerErrors is null

The following shows an example display of an OpenAccess ORM error:

c:\program files\Telerik\OpenAccess ORM\examples\ExamplesWin\Caching'Caching.cs: error CS0103: The name 'discountRate' does not exist in the class or namespace 'BusinessObjects.Customer' Build complete -- 1 error, 0 warnings

Double-clicking on the error positions the cursor on the corresponding class definition.

A solution build displays the following output:

OpenAccess ORM All: 1 succeeded, 0 failed, 0 skipped

The number of skipped OpenAccess ORM projects is the number of projects where the Enhancing project property is set to false.

The Task List window

All OpenAccess ORM warnings and errors are reported to the Task List. They are categorized under the task Build Errors, which is the default task in Visual Studio and are displayed when any compile errors occur. They are also visible in the All category. In order to distinguish .NET compiler errors from OpenAccess ORM enhancer errors, all the OpenAccess ORM enhancer errors are displayed with the prefix "OpenAccess". Double-clicking on an OpenAccess ORM enhancer error or warning displays the corresponding source file with the cursor positioned at the beginning of the class definition (this might not be on the exact line where the error occurred). The error description gives detailed information about the position and the reason for the error.