Skip to content

Updating a File Inside the Package

This is how to make the changes that Changes You Can Make marks as needing the base package updated. The change is made under ProgData, at the same path the file occupies on the machine.

  1. Note the full path of the file you changed on the machine, for example C:\Program Files\Example\settings.config.

  2. In the base package, open ProgData and follow the same path. How the drive letter appears depends on when the Compatibility Package was built: newer packages carry it as a folder, older ones omit it. Check which shape your ProgData uses and follow that one. For the example above:

    ProgData\C\Program Files\Example\settings.config    (drive letter as a folder)
ProgData\Program Files\Example\settings.config      (drive letter omitted)

  3. Take a copy of that file before changing it, so the previous version can be restored.

  4. Make the same change you made on the machine, and save it.

Note: Only ProgData is edited this way. Do not change the configuration files in the package root: they are covered by the package's licensing hash, so editing one invalidates the licensing tokens and the Compatibility Package stops deploying or running until Cloudhouse re-licenses it. If the change you need is not under ProgData, it is one for us to make. See Changes Cloudhouse Must Make.

Recommended Approach

The steps above change the Compatibility Package every future deployment is built from, so it is worth making the change in a way you can undo and check:

  1. Take a copy of the base package, or at least of the file you are about to change, before you touch it.
  2. Make the change in the base package first, rather than only on a machine, so the two never diverge.
  3. Redeploy one machine from the updated base package and confirm the application behaves as expected, before rolling the change out more widely.
  4. Keep a short record of what you changed and when. It is the first thing anyone will want if the application misbehaves later.
  5. If you are not certain whether the Compatibility Package carries the file, or the change is not under ProgData, send us the detail and we will make it and reissue the Compatibility Package.

Related Pages