Skip to main content

.NET

To enable .NET developers to leverage the scalability, connectivity, and reliability of the InterSystems IRIS for Health™, InterSystems IRIS for Health supports several types of connections to and from .NET applications.

Get acquainted

video icon.NET OverviewOpens in a new window

documentation iconUsing .NET with InterSystems Software

Try it

interactive icon .NET QuickStartOpens in a new window

interactive iconExperience .NET and InterSystems IRISOpens in a new window

interactive iconDesigning a .NET Connection StrategyOpens in a new window

Navigation icon.NET IDEs

Connect a .NET application to InterSystems IRIS

ADO.NET for relational access

ADO.NET is a data access technology from the Microsoft .NET Framework that enables programmers to access data sources in InterSystems IRIS for Health™ with SQL in a standard, reliable way.

interactive iconFirst Look: ADO.NET and InterSystems Products

external link icon ADO.NET overviewOpens in a new window

XEP API for high-speed object access

The XEP (Express Event Persistence) API provided by InterSystems enables .NET applications to store and retrieve objects from InterSystems IRIS for Health™. More specifically, XEP projects .NET objects as persistent events, which are persistent database objects that store the state of .NET objects.

XEP is optimized for applications that must handle high throughput, such as transaction processing applications. If you use XEP for object persistence, you can avoid the overheard of object-relational mapping.

video icon Using XEP with .NETOpens in a new window

interactive iconFirst Look: .NET Object Persistence with XEP

documentation icon Persisting .NET Objects with InterSystems XEP

documentation iconInterSystems IRIS XEP JavadocOpens in a new window

Native API for direct access to data

The Native API for .NET provides direct access to globals, the tree-based sparse arrays that form the basis of the InterSystems multidimensional storage model and underlie the InterSystems IRIS for Health™ object and SQL interfaces. The Native API exposes these native data structures, which provide very fast, flexible storage and retrieval. The Native API also enables your .NET application to work with InterSystems IRIS for Health objects as easily as if they were native .NET objects, and includes the ability to call InterSystems IRIS for Health class methods and routines.

video icon Using the Native API for .NETOpens in a new window

interactive iconFirst Look: InterSystems Native API for .NET

documentation iconUsing the InterSystems Native API for .NET

Navigation iconNative APIs

Entity Framework for object-relational mapping

Entity Framework is a mapping tool that enables you to map .NET objects to relational tables in InterSystems IRIS for Health™ and eliminates the need for most of the data-access code that developers must typically write.

interactive iconUsing Entity Framework with InterSystems IRIS)Opens in a new window

external link icon Entity Framework documentationOpens in a new window

Connect InterSystems IRIS to an external application

documentation iconUsing the Object Gateway for .NET (for instantiating and manipulating external .NET objects)

documentation icon Using the InterSystems SQL Gateway (for connecting to external databases via ODBC)

documentation icon Using the InterSystems ODBC Driver (for connecting to external ODBC data sources)

Explore more

interactive icon First Look: The InterSystems .NET Gateway

interactive iconStock Trading with .NETOpens in a new window

interactive icon Skyrocket Your .NET Application DevelopmentOpens in a new window

documentation icon.NET IDEs

external link iconMicrosoft .NET DocumentationOpens in a new window

FeedbackOpens in a new window