wix - What is the MSI component generation best practice? -

visual studio installer states best practice install each file installer component. heat utility provided wix seems follow practice of putting every file in own component.

installshield's component wizard uses installshield's setup best practice of placing portable executable files in own component groups other files (e.g. unversioned files) common destination folder.

the advantage of practice 1 (each file in own component) each file set key file important if want these files trigger repairs. allows automation of creating components (e.g. heat) easier since creating component each file.

the disadvantages of practice 1 include overhead of managing many components , bloating of registry after application installed.

an advantage of practice 2 seen in install installs hundreds of graphics files 1 directory. if not care repair functionality, there reason create hundreds of components install?

these 2 different practices conflicting , want know 1 people use , why.

i use microsoft approach (something similar installshield does): http://msdn.microsoft.com/en-us/library/aa368269(vs.85).aspx

i think it's best because: - important files (exe, dll etc.) have own component, can repaired - resource files grouped - allows optimum components count (not many long install, enough allow easy repair)

i noticed commercial setup authoring tools use approach.