Setting Up Environment

Last Updated: 12/05/2015 Introduced in Verision: 2.0
Most of the examples and sdk functionality described in this document involve providing a DLL (library) that has additional functionality in it.  This DLL can be built in any tool or language that can construct a .NET library – but our examples are going to be using Visual Studio (2010) and c#.
 
While different .NET assemblies may be used in your classes the only dll that is needed to be included is DecisionsFramework.dll.  If you have the Decisions SDK installed, this dll can be found in C:\Program Files\Decisions\SDK\Backend\DecisionsFramework.dll . If you only have Decisions platform installed, this DLL can be found in  C:\Program Files\Decisions\Decisions Services Manager\bin .
 
To install the Decisions SDK, make sure the file Decisions.SDK.x64.msi (or Decisions.SDK.x86.msi if you are doing a 32-bit installation) is in your installation directory and check the SDK option on theAdvanced Settings page of the Decisions Installer.
 checkSDK
 
 
 

If Decisions is already installed and we want to install SDK without Decisions re-installation, we need to follow the next process.

First, we navigate to http://releases.decisions.com/Releases web page.

 releasesDecisions

Next, we select our current build. Then, we pick our build family…

 selectBuildFamily

In the resulting web page we click Browse Files.

 browseFiles

From the resulting web page we download Decisions.SDK.msi file…

 decisionsSDKmsi

Then, we run this msi file and follow Wizard instructions…

 decisionsSdkWIzzard

First, we confirm the Agreement.

 Sdk

Then, we select desirable folder to install to, and click Next

 decisionsSdkFolder

Click Install to start installation process…

 installSdk

After Installation finishes…

 installationSdk

We click Finish to close Installation Wizard.

 finishSdk
 
Other common dlls that are referenced include:
System.xml
System.componentmodel
System.serialization
System.Serialization.soap
 
Any additional 3rd party dlls can be included.  Any included dll must also be deployed along with the one containing classes that are extensions to the platform.

Additional Resources