Used the repackager for a client-provided EXE so I could get a useful MSI, but when I tried running the app after installing the MSI, it told me there was missing registry info and wouldn't run.

So is there any way I use the recipe file to add back in some of the registry items I excluded? Or am I going to have to start from scratch?

When I select "Build packages based on existing recipe file", the screen that lets me review the contents of the Recipe file doesn't appear to allow me to make any changes to the package. The "Update Files" and "Rescan Registry" buttons never activate, so I'm not sure as to how to proceed with a second try at creating the MSI.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


No, the recipe file is for building a package without the need to perform a snapshot (leveraging someone else's work). As such, it does not store excluded items. You can either:

  • create a new package
  • edit the MSI to add the additional items with an MSI editor
  • edit the XML recipe file to add the additional items (then use it to build an MSI)

The screen to review the file and registry items shown when building an MSI based on a recipe file exists only to help you ensure all expected file and registry items are accounted for. Assuming you got the recipe from someone else, this lets you ensure any file and/or registry entries are found so they may be compiled into the resulting MSI. Seeing as you created the recipe, I would assume all file and registry items are accounted for (so adding files or rescanning the registry for missing items is not necessary).
Answered 02/20/2009 by: bkelly
Red Belt

Please log in to comment