This is one of the many reasons visual studio deployment projects were removed from VS2012. VDPROJ can only schedule custom actions in the deferred phase of the installation execute sequence. This is not an appropriate place to perform user interaction. Windows Installer is designed to perform UI first in the installation user interface sequence and then transfer control to the execute sequence. In a silent installation only the execute sequence is performed.
If you need custom UI you either need to go down a very complicated road of postbuild manipulations of the MSI to inject capabilities not exposed by VDPROJ or switch to a tool such as Windows Installer XML (WiX) of InstallShield Professional Edition that exposes this.
See the following for a better understanding of MSI:
Installation Phases and In-Script Execution Options for Custom Actions in Windows Installer