You can only do this sort of thing in the program itself. So it would have to happen AFTER installation.
You could have an extra form "frmSettings" which is the first to load and asks all neccessary questions. Then it could update a registry setting (maybe FirstRun="NO".
When your app runs you must check this setting and only load the "frmSettings" form if the registry entry First run is not "No" or doesn't exist.
If you must ask the use for input before/during installation you'll have to use something better than the deployment wizard that comes with VB.
The source code for the setup program can be found in C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Setup1 (or similar). you can modify this to include additional setup functions, compile it and put the setup1.exe file into the C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard folder. the package and deployment wizard will use this version of the setup1.exe program during the install process.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.