InRule Leading .NET Integration

While supporting .NET simply means that an application will run reasonably well, exploiting .NET means the application takes advantage of many .NET-specific capabilities that can only be leveraged when the application is designed for a .NET environment and built by .NET experts. InRule™ was designed, built, and optimized for .NET. As the premier rule engine for .NET, InRule delivers many capabilities that the generic vendors can't.

InRule's .NET capabilities allow your development teams to utilize code they've already written and work with InRule in a development environment that is familiar to them. With just a few lines of code using irSDK, developers can add InRule functionality into new and existing applications. And because InRule was designed and optimized for the .NET platform, you can be assured that your team won't bump up against the limitations imposed by other platforms.

From Supporting .NET to Exploiting It

Why .NET Developers Love InRule™

Many rules engines claim support for multiple environments, including .NET. Some
vendors may have started with a Java-based solution, ported the code to .NET and
then attempted, over time, to deliver equal capabilities on the .NET platform.
Because InRule™ is the only business rules software designed, built and optimized
for .NET, it offers capabilities that go beyond generic vendors.
InRule Technology Knows .NET

Focused entirely on .NET customers, InRule Technology invests all its research and
engineering resources on the .NET platform. Our company was founded by
recognized leaders in the .NET community. Co-founder Loren Goodman, InRule
Technology's Chief Technology Officer, is a Microsoft MVP and a member of several
prestigious groups that provide advice and input to Microsoft, including the:

.NET Partner Advisory Council
Microsoft Architecture Advisory Board
Smart Client Working Group

Your Developers Know .NET

InRule's .NET capabilities allow your development teams to utilize code they've
already written and work with InRule in a development environment that is familiar
to them. With just a few lines of code, developers can add InRule functionality into
new and existing applications. And because InRule was designed and optimized for
the .NET platform, you can be assured that your team won't bump up against the
limitations imposed by other platforms.

What Supporting .NET 3.0 Actually Means

Supporting .NET simply means that an application will execute within the .NET
framework. If you have the .NET 3.0 framework installed,.NET 2.0 applications will
run on it.

The .NET Framework 3.0 is a superset of the v2.0 framework, adding Windows
Workflow Foundation (WF), Windows Communication Foundation (WCF), Windows
Presentation Foundation (WPF) and Windows CardSpace.

All InRule Technology products are optimized for v2.0 of the .NET Framework, and
run without modification on v3.0. Some products such as InRule for Windows
Workflow Foundation, already leverage some of the v3.0 features.

What Exploiting .NET Means

While supporting .NET simply means that application will run, exploiting .NET means
the application takes advantage of many .NET-specific capabilities that can only be
leveraged when the application is designed for a .NET environment and built by .NET
experts.

InRule™ was designed, built, and optimized for .NET. As the premier rule engine for
.NET, InRule delivers many capabilities that the generic vendors can't.
From Supporting .NET to Exploiting It

Why .NET Developers Love InRule™

NET Classes, Schemas, and DataSets. InRule can use .NET classes, XML Schemas and DataSets to derive and maintain schemas. Because business users can harvest schemas from existing sources rather than trying to recreate them, authoring takes less time and is more accurate.
.NET Object Graphs. InRule executes against .NET object graphs at runtime, acknowledging relationships among objects in the graph.
.NET Collections. As part of this capability, InRule supports native .NET collections. For example, a policy may contain a collection of borrowers, each of which contains collections of assets and liabilities.
.NET Assemblies. InRule irSDK includes a set of .NET assemblies that contain InRule functionality that developers can easily embed within their own applications. Intuitive and requiring no additional tools to install, irSDK enables .NET developers to drop InRule controls (such as decision tables and the business language editor) into .NET applications.
.NET DataSets. Organizations that have adopted .NET as their development platform may have standardized on .NET DataSets, which InRule can also operate against natively. Without this native support, additional code to manage data must be written and maintained— resulting in significant overhead to development resources and potentially slower performance.
.NET Events. Events that occur in InRule are exposed to consuming code using native .NET Events, either during rule execution or upon completion. For example, a rule author may indicate that the rule engine should raise a .NET event when certain conditions are met and pass data to the application executing rules. This allows the developer to perform an application-specific action when those conditions are met during rule execution.

By exploiting the capabilities of .NET using techniques .NET developers are familiar with, InRule enables IT to quickly deliver applications that are easy to understand and maintain.