Repackager

[CChong]

When the Repackager is installed on the Packager's machine and you create a package (classic mode or monitoring)and you specify that the project will replace the files with the merge Modules, instead the project installs the files and also the merge modules.

Is this the expected behaviour ?

[RajeshTammana]

It is a good practice to install merge modules if avalable instead of installing the individual files.

If you select the option of "replace with merge modules" then individual files should not be available in the project.

[CChong]

In our environment a decision has been made to include all the merge modules into the build routine of the workstations;
ie: forms part a "common controls and libaries" package -so that infact the merge module files is already included as part of the os (workstation image)

This allows us to maintain / update the merge modules globally across the company with the OS updates as opposed to maintaining the merge modules on a per application basis.

So let me reword my orginal posting:

When the Repackager is installed on the Packager's machine that has pre-installed merge modules and you create a package (classic mode or monitoring)and you specify that the project will replace the files with the merge Modules, instead the project installs the files and also the merge modules.

Is this the expected behaviour ?

[RajeshTammana]

Could you provide more information to debug this issue:

Usually merge modules contains the same files that are used inplace of the actual files.

When you say that project install both files and merge modules, are you seeing two copies of the physical files when you install the Windows Installer pacakge?

[CChong]

Feedback from our packager:

You will see the merge module box checked as appropiate, depending on the application requirements plus you will have listed the files relating to the merge module included in the identified snapshot files.