• InRule Leading .NET Integration

    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.

    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 Version 4 is built on .NET 4.0 and takes advantage of key capabilities in Windows Presentation Foundation (WPF), Silverlight 4, and the Parallel Extensions. 

    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.

    InRule Knows .NET

    Because InRule is the only business rules solution designed, built and optimized for .NET, it offers capabilities that go beyond generic vendors. 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.

    Why .NET Developers Love InRule

    • irAuthor Extensibility model makes it easy for .NET developers to add, remove or augment irAuthor functionality.
    • irStudio allows .NET developers to author InRule rules from within Visual Studio
    • Silverlight authoring controls enables .NET developers to create web-based authoring environments
    • NET Classes, Schemas, and Databases. InRule can use .NET classes, XML Schemas and Databases 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 Objects. InRule executes against .NET objects at runtime, acknowledging relationships within the object 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 SDK. 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.
    • Rich runtime integration: At runtime, the InRule rules engine can interoperate with .NET objects and static methods, web services, database, workflows, XML documents and more 

    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.