With installer issues it's always difficult debug problems. If it's the Installer itself i.e. work done in the setup.vdprj itself then you maybe in a spot of bother. There are some logging options which are available to you.The other problem you may have is with your Custom Action if you have one. This maybe easier to diagnose, asyou can use the Visual Studio Debugger to attach but this in itself is not always easy todo. If you have problems with your installer itself and not the Custom Action then try this: You can also Log installer actions by activating the installer logging, this is done through a registry entry, http://support.microsoft.com/kb/223300 . All your doing is adding a "String Value" named "Logging" and a value "voicewarmupx" to the registry entry HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer I've done this and found some useful info but it's not that easy to read, at least it tells you the command that was...
Layman explanations of Software coding and configuration techniques. With example code where possible.