EndPoint Assemblies Folder

.NET assemblies that are referenced from rule applications must be accessible to the rule engine for execution.  Referenced assemblies could include static function libraries, bound business objects, and referenced type libraries.  InRule will check several locations, in order, to locate any referenced assemblies.

For in-process connections, the default folder locations for InRule to check for assemblies during execution include the following:

• irVerify: InRule\irAuthor\EndPointAssemblies
• Custom .NET application: the application's bin directory

For out-of-process connections, the default folder locations for InRule to check for assemblies during execution include the following:

• IIS: InRule\irServer\RuleEngineService\IisService\bin\EndPointAssemblies
• Windows Service: InRule\irServer\RuleEngineService\WindowsService\EndPointAssemblies

Other locations where assemblies may reside include the following:

• Global Assembly Cache (GAC)
• A user defined directory which is designated by adding the following setting to the application config file:

 <appSettings>
<add key="inrule:repository:endPoints:assemblyEndPoint:endPointAssemblyPath" value="EndPointAssemblies">
</appSettings>        

OR

   <configuration>
     <configSections>
       <section name="inrule.repository" type="InRule.Repository.Configuration.RepositoryConfigSectionHandler, InRule.Repository" />
       ...
     </configSections>
     ...
     <inrule.repository>
       <endPoints>
         <assemblyEndPoint endPointAssemblyPath="EndPointAssemblies" />
       </endPoints>
     ...
     </inrule.repository>

InRule checks folder locations for assemblies in the following order:

1. Global Assembly Cache (GAC)
2. Location specified in config file
3. EndPointAssemblies folder
4. The calling application's binaries directory (.NET only)