How to Deploy New Orders Assemblies and Mapping Files
If you write code to extend the Orders system, you must create and deploy a new assembly to integrate your code with Commerce Server Core Systems. You can deploy any .NET assembly, including a Commerce Server Core Systems assembly, in two ways: locally, or through the global assembly cache (GAC). If other applications will need to use the assembly, you must install the assembly in the GAC. For more information about the GAC, see https://go.microsoft.com/fwlink/?LinkId=64427.
If you modify the Orders mapping files — either the OrderObjectMappings.xml file or the OrderPipelineMappings.xml file — you must configure Commerce Server Core Systems to use the updated files.
This topic contains procedures for deploying a new Orders assembly and deploying new Orders mapping files on a single Web server. If your application is deployed on multiple Web servers, see Commerce Server Staging for more information about how to deploy your assembly and mapping files on multiple Web servers.
To deploy a new Orders assembly locally
Copy the assembly to the virtual root of the Web server.
Update both the Web.config file for your application and the Web.config file for the Orders Web service.
Update the Types element in Web.config file to reference the new assembly. Update both the Web.config file for your application and the Web.config file for the Orders Web service.
If you created a new version of an existing class, update the SerializationBindings element in the Web.config file. Update both the Web.config file for your application and the Web.config file for the Orders Web service.
To deploy a new Orders assembly through the GAC
Sign the assembly with a strong name. For more information about signing an assembly, see https://go.microsoft.com/fwlink/?LinkId=64428.
Run gacutil.exe to install the assembly in the GAC. For more information about gacutil.exe, see https://go.microsoft.com/fwlink/?LinkId=64429.
Add a new add element to the assemblies element within the compilation element in the Web.config file to identify the new assembly. Update both the Web.config file for your application and the Web.config file for the Orders Web service.
Update the Types element in Web.config file to reference the new assembly. Update both the Web.config file for your application and the Web.config file for the Orders Web service.
If you created a new version of an existing class, update the SerializationBindings element in the Web.config file. Update both the Web.config file for your application and the Web.config file for the Orders Web service.
To deploy new Orders mapping files
- If you renamed or modified the mapping files, update the MappingFiles element in the Web.config file. Update both the Web.config file for your application and the Web.config file for the Orders Web service.