AI can do per-build Features, which is very nice. I am trying to use this functionality to make a single install project with platform-specific builds (x86, amd64, ia64 builds). This is a per-machine only product that can never be installed side-by-side, and the 32-bit version will refuse to install on 64-bit Windows (also see [2] below), so there should not be any ProductCode conflicts.
1) For my use, per-build components would be highly useful. I could simply add 3 components to one feature (x86, amd64, ia64 versions) and select in which build each component should be included. I do this now by adding 3 per-build Not Displayed + Follow Parent features under one containing feature which the user will actually see. So, essentially, I am already using per-build components, they are just wrapped by features. This works but is awkward and has its drawbacks: a lot of otherwise unnecessary features to manage; the containing feature ends up not having any components of its own and the Windows Installer shows Run from CD/Run from network as an allowed install state for it.
2) Right now I am using a custom Launch Condition to prevent the x86 build from being installed on 64-bit Windows versions. As such, I think per-build Prerequisites would be really nice too. This would make sense especially since Package Type is a per-build property already.
Thank you for your consideration!