DLLs and dependencies
Luckily, having read the rest of this topic, there is little else you need to know.
Because we're working with . NET now, there are of course no JAR files. Instead,
i BATIS.NET Data Mapper is deployed as DLL files that you need to include as refer-
ences in your assembly. Like its Java sibling, the . NET version has very few depen-
dencies. In fact, only three DLL s are required; see table A.1.
iBATIS.NET has dependencies only on these three assemblies.
The common utilities of the iBATIS.NET framework. Generally these
common classes are shared between the iBATIS Data Mapper and
Data Access frameworks.
IbatisNet.DataMapper.dll The core classes for the iBATIS.NET data Mapper. Contained within are
the classes that you will most often use to interact with iBATIS.NET.
One of only two third-party dependencies, Castle Dynamic Proxy pro-
vides functionality to support dynamic extension of classes and imple-
mentation of interfaces at runtime. iBATIS uses such proxies for lazy
loading as well as automatic transaction management in some cases.
The XML configuration file
i BATIS.NET has an XML configuration file, just as i BATIS for Java does. The struc-
ture of the file is a bit different, but it's similar enough that you can no doubt
understand it. All of the configuration files are validated by XSD schemas. If you
install the XSD for these files in Visual Studio, you will gain the benefit of having
IntelliSense support. This will make coding these files a lot easier. See the Visual
Studio documentation for information on installing XSD files. Listing A.1 shows a
sample i BATIS.NET configuration file for a simple application.
SqlMap.config XML configuration file
<?xml version="1.0" encoding="utf-8"?>
<!-- Database connection information -->