Using InRule NuGet Packages

  • Updated

When you install irSDK, NuGet packages for the SDK assemblies will also be placed in a "NuGetPackages" sub-folder.





Support for using InRule with Windows Workflow Foundation.


Core Authoring SDK assemblies used for creating irAuthor extensions. This package is also required for creating custom authoring applications.


Authoring SDK assemblies used for creating custom authoring applications. Includes assemblies needed at runtime when executing outside irAuthor. irAuthor extension developers do not need this package and should use the InRule.irAuthor.SDK package instead.


irSDK Authoring assemblies used for irAuthor extensions. This is a metapackage with dependencies on other packages needed for extension creators.


Common irSDK assembly used for integration with InRule®.


Common Repository irSDK assemblies used for authoring and/or runtime integration with InRule®.


Runtime integration with the InRule® Rule Engine.


Assembly to facilitate mapping between InRule Entities and Salesforce® Platform objects.



The packages are licensed under the standard InRule End User License Agreement and the packages metadata includes a link to this license.  Installing the packages via most NuGet clients will require you to explicitly accept the license.

When executing applications that consume these assemblies, the associated InRule license must be activated.

Package Dependencies

In most cases, packages will depend on other packages based on the assembly dependencies.  For example, installing the InRule.Authoring.Core package will install the Authoring SDK assemblies, and it depends on the InRule.Repository package in order to also install InRule.Repository.dll. The InRule.Repository package depends on the InRule.Common package, which contains InRule.Common.dll.  It is generally only necessary to install the specific package you need for your development scenario (InRule.irAuthor.SDK or InRule.Runtime, for example) and allow the dependencies to install the remaining packages, if any.

Dependencies are set to specific versions, so if you upgrade a single package, all of the InRule packages will also upgrade at the same time in order to meet the dependency requirements. Typically, your NuGet client will handle this for you.


The package versions will match the first three digits of the InRule product version number.  Only the first three digits are used to conform to the Semantic Versioning rules enforced by NuGet.

Consuming the Packages

While you may choose to publish the packages to your own private NuGet server, InRule does not publish the packages to a public NuGet repository.  If you do not wish to host your own NuGet server (or use a third party service to host a private server), you can use a file folder as a NuGet source.

In Visual Studio, you can do this by going to the NuGet Package Manager and clicking the gear icon next to the Package Source list, or going to the Visual Studio Options and selecting "Package Sources" under "NuGet Package Manager"


This will open the NuGet package sources options. Click the "+" icon to add a new source, then in the "Source" field, use the "..." button to browse to the folder holding the NuGet packages:


Click "Update" and "OK" to save the changes. Back in the NuGet Package Manager, in the "Package Sources" drop-down, select the new location (or "All") to include the packages in that folder in your NuGet repository.


Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.