When deploying a patch, if one follows the Worksoft Certify README instructions correctly, there are no problems.However, sometimes, the IT department has a different policy and tries to disassemble the patch and deploy the patch themselves. There are many variations of what can go wrong. One of them is listed here.
Problem: The user renames old Certify interface packages and copies the new interface packages into the client folder.
Results: Renaming the old Certify interface packages (*.manifest and *.package files) would not stop it from deploying. The user can end up with incorrect (older) dlls instead of the new dlls. Symptoms can range from a failure during execution or a problem with Livetouch and/or Learn tools.
Recommendation:
1. Please do not rename the Certify interface packages.
2. If you have already done so and have gotten an incorrect deployment, you may start over by.
- Removing all the old Certify interface packages.
- Make sure that only the new Certify interface packages remains.
- Delete the PackageDeploymenthistory.XML file (See more at http://community.worksoft.com/wikis/certify/how-to-force-the-certify-interface-patches-to-redeploy-packagedeploymenthistory-xml.aspx)
- Start over with the patch deployment and follow the steps in the patch README file.