📄️ Common Integration Scenarios
Sample approaches for implementing InRule on common .NET technology stacks: Web Services, ASP.NET MVC, BizTalk, Dynamics, and more.
📄️ Web Services
The most popular InRule integration approach: a WCF or Web API service hosting the rule execution SDK as a reusable service layer.
📄️ ASP.NET MVC
Integrate InRule with ASP.NET MVC web applications, running in-process and binding directly to .NET types, including Entity Framework types.
📄️ BizTalk
Integrate InRule with BizTalk using InRule's BizTalk adapter, which can run within a BizTalk Host.
📄️ Dynamics CRM
Integrate InRule with Microsoft Dynamics CRM, running rules against CRM entities via a lightweight on-premise plugin or reusable service.
📄️ SharePoint
Call InRule from SharePoint event handlers, workflows, WebParts, and farm Pages, optionally via a reusable rule service.
📄️ Entity Framework
Integrate InRule with Entity Framework and other ORMs, running rules directly against Entity Framework entity types.
📄️ Enterprise Rule Services
Build atomic business logic services that run InRule in-process using REST, combinable across various enterprise business processes.