• Introduction
• • Introduction
  • Features
  • CS Connector
• Getting Started
• • Installation
  • Development Tasks
  • CS Integration
  • Integration Issues
• Runtime
• • Configuration
  • Promo Codes
  • Pipeline Output
  • FAQ
• Promotion Customisation
• • Promotion Events
  • Single Gift Promotions
  • Gift Selection Promotions
  • Gift with Purchase (2.7+)
  • Basket Addition Selection (2.7+)
• Promotion Marketing
• • Promo Shout Outs
• Deep-Dive Guides
• • Gift Promotions
  • Tracing with PerfView
• Go-Live Guides
• • Discount Engine Switch
  • Go Live Checklist
  • Deploying an Update

Developer Documentation

Deploying an Enticify Update

This guide explains how to deploy new versions of Enticify.

Important: You must previously have installed Enticify, using the Enticify.x64.msi or Enticify.x86.msi installer.

• Receive a new Enticify release from us, e.g. Enticify-3.0.0.0(4.0.4)-2009.zip.
• Note that the 3.0.0.0 part of the zip file name is the Enticify AssemblyVersion.
• If the AssemblyVersion has changed since you last ran the msi installer, or you're happy to run the installer again regardless, do the following:
  • Uninstall Enticify via the Windows Programs Control Panel.
  • Install the new version, using the provided msi installer.
  • You're done.
• If the AssemblyVersion has not changed and you'd like to XCopy deploy, you can do the following:
  • Note: You must work out if the following is OK, in the context of your app and infrastructure design.
  • XCopy the Enticify.CommerceServer.dll assembly over the \Program Files\Enticify\bin\Enticify.CommerceServer.dll assembly.
  • XCopy the Enticify.CommerceServer.dll assembly over any other copies of the assembly. This would usually be in your web application or services that reference Enticify and have copied it locally.
  • Recycle processes using the assembly, as required.
  • You're done.

Notes:

• We increment the AssemblyFileVersion to reflect the real Enticify version you have. The fixed AssemblyVersion is a known workaround for avoiding the need to update COM registrations.
• We do our best to change the AssemblyVersion as little as possible, but you MUST run the installer if the AssemblyVersion changes.
  
• Sometimes we will advise you to run the installer, even when the AssemblyVersion has not changed. For example, we might include new resources in the installation, such as we did with PerfView.