Oh yeah, to validate the value just change your condition to require what you want.
For example: field1 = (value1 | value2 | value3 | etc...)
Main Topics
Browse All TopicsI have created a project in vb .net 2003. I also created a setup project for the deployment of this project, I am using a textbox type dialogbox (in userinterface section) to to get a certain value while installation. Everything works fine... i get the value and use it. but the problem is "I want to make that textfield mandetory". During installation if i dont enter anything in the textbox the project still installs. i want user to enter a value if they want to continue installaion.
Also is there any way to validate the value?
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: abhatnagarPosted on 2007-03-15 at 09:06:57ID: 18728087
Simply set a condition on the field. So when it is field<>NULL then enable your next button to move on. Otherwise, disable your next button by default. Be sure to test what happens when the end-user bypasses the UI sequence by running the MSI via command line.
Best of luck.