docs.intersystems.com
Home  /  Application Development: Language Bindings and Gateways  /  Persisting .NET Objects with InterSystems XEP  /  Introduction


Persisting .NET Objects with InterSystems XEP
Introduction
[Back]  [Next] 
InterSystems: The power behind what matters   
Search:  


XEP is a lightweight API that provides high-performance .NET technology for persisting simple to moderately complex object hierarchies. XEP projects the data in .NET objects as persistent events (database objects that store a persistent copy of the data fields) in an InterSystems IRIS™ database. XEP is optimized for applications that must acquire and persist data at the highest possible speed.
InterSystems IRIS™ provides .NET APIs for easy database access via either objects or relational database tables. This book discusses the API for object access. See Using the InterSystems IRIS Managed Provider for .NET for relational table access.
Requirements and Configuration
The following sections provide instructions for including XEP when installing InterSystems IRIS, and for configuring your environment to use the XEP API.
Requirements
Computers that run your .NET client applications do not require InterSystems IRIS, but they must have a connection to the InterSystems IRIS Server and must be running a supported version of the .NET Framework.
Installation
Configuration
Your .NET project must include references to the following files. Different versions of these files are located in appropriately named subdirectories of <install-dir>/dev/dotnet/bin (for example, <install-dir>/dev/dotnet/bin/v4.0.30319 contains the file for .NET 4.0). Use the appropriate files for the release that will be used to compile your project:
In order to run XEP applications:
XEP Sample Applications
XEP sample applications are available from GitHub (see “Downloading Sample Applications from GitHub”). To run them, compile the project as described in the ReadMe file. The project includes the following components:
The sample package includes supporting files that provide test data for the applications. See the help files included in the sample package for detailed documentation of these programs.
RunAll.cs connects to InterSystems IRIS with a default superserver port value of 51773 (see DefaultPort in the Configuration Parameter File Reference). If your system does not use this default value, you can specify the superserver port as a command line parameter.