I don't think the "Force installation of this prerequisite" condition works if the prerequisites' UI Level is set to "Basic UI and progress." If the prereq install is canceled, the application installer continues regardless. It might also continue if the prereq has errors, though I couldn't test this.
How to reproduce:
1. Create a new professional project.
2. Add the .NET Framework as prerequisite software using a local file (you'll need the actual installer for this, obviously).
3. Set the minimum version to something high so that it can't be fulfilled--say, 4.0.
4. Set the UI level to "Basic UI and progress."
5. Add a text file or something to the install so that you can build it.
6. Build and run the project. The .NET framework installer will launch.
7. Cancel out of the .NET installer.
8. Watch as the rest of the application installer happily continues, oblivious to the missing prereq.
You can work around this with a launch condition, but it still seems like a bug.
FOLLOW US
Get the latest news in Application Packaging