I have a Visual Studio setup project that is built using Team Build. It has an extremely annoying habit of adding a duplicate assembly to the installer for an assembly that is already included in the installer as a project output. I am constantly having to check that the duplicate is excluded from the setup project but frequently the output from Team Build still includes the duplicate assembly. If this occurs, the install will fail with a message that it cannot write the duplicate to disk, because it has already just written the correct one and hasn't yet released the file handle.
I assume it is possible with Orca to remove the duplicate assembly from the installer which I'm contemplating doing in order to maintain a reasonable accord with the guy who has to run the installer. What do I need to do to remove an assembly from the installer?
Assemblies are usually added in two tables: File and MsiAssembly. So you can try removing the appropriate rows from these tables.
However, the best solution would be to determine why the assembly is added twice and prevent that action. Modifying the MSI after build it treating the symptoms, not the cause.