More information on the issue we're trying to solve:
We need the ability to patch non versioned files /delete them if necessary,
etc. (in an MSP) We have found information indicating that removing the
ComponentID in the MSI will cause the Windows Installer to treat these
components as User D
Problem: dll won't update with an MSP.
History:
Released MSI with a language MST applied. The version information in the file
table is removed by the MST AND the dll has an entry in the MSIFileHash table.
Applying an MSP to update this dll ( the updating dll and MSP include valid
version inf
2 matches
Mail list logo
