Assemblies Required by a Client Application
You can create a DCS client application by using any of the standard .NET Framework application types, including Windows Forms–based applications, console applications, and WPF applications. A client application references specific DCS assemblies to access the DCS runtime. The application must also reference assemblies that the deployment utilities create during the DCS service deployment process, which contain the proxy and message objects that are required to invoke the DCS service. For more information on the deployment process, see Deploying DCS Services.
Note
DCS requires the .NET Framework 3.0, Service Pack 1 or later. You must make sure that you have installed this version of the .NET Framework on all computers that will run DCS client applications.
Required DCS Assemblies
A DCS client application requires the following assemblies that DCS provides:
- Microsoft.ConnectedIndustry.ServiceModel.ClientCache
- Microsoft.ConnectedIndustry.ServiceModel.Common.dll
- Microsoft.ConnectedIndustry.ServiceModel.WorkflowClientBase.dll
These assemblies are located in the <DCSinstallation directory>\Microsoft CIS\DCS\V1.0\Bin folder. You should add them to the client project.
Required .NET Framework Assemblies
To enable your application to serialize and deserialize messages correctly, you must add a reference to the System.Runtime.Serialization and System.Xml assemblies. Although you do not need to use the namespace or write any serialization code yourself, some of the code in the DCS proxy object, including the code that handles Request and Response messages, requires these assemblies.
You should also add a reference to the System.ServiceModel assembly.
DCS-Generated Assemblies
When you deploy a DCS service, the deployment utilities place several assemblies in the DCS Repository folder. These assemblies include the messages that you created when you generated the service, a service assembly that contains the compiled service code, and a service proxy assembly that contains the proxy object that client applications should use to invoke operations in the service.
To call correctly into your DCS service, you must add a reference to the message assembly and the service proxy assembly to your client application.