Hi,

I am creating a Setup and Deployment project for creating a Windows Installer. I have to check for pre-requisites of SQL Server, If SQL Server is not installed i have to abort the installation. I did this using the Launch Condition Editor, but soon after I run the .msi the error message pops up saying SQL Server is not installed, before the Welcome screen appears. I want the error message to pop up after the welcome screen.

Also I tried writing a custom action which throws error message if SQL Server is not installed, this message pops up only when starting installation, but soon after my error message comes, another message is thrown my the installer itself. I dont want this message thrown by the installer topop-up. How can I avoid this?

Any help will begr8!

Thanks,

Uma

Launch Conditions are prerequisites for the installation to proceed, and the behavior you see is normal. Not only is it normal behavior with many setups, it's also the way Visual Studio generates the launch conditionsand you can't change them.

Also, understand that Visual Studio custom actions happen after the installation, not before, so by the time you do your checkin a custom action the setup is pretty much finished, and if you abort it then it will roll back. Your choices are leave the behavior as it is, use another tool that has the features you want and build your MSI file with it, or learn enough about the content of an MSI file to post-process it with an MSI editor like Orca.

Launch Conditions are prerequisites for the installation to proceed, and the behavior you see is normal. Not only is it normal behavior with many setups, it's also the way Visual Studio generates the launch conditionsand you can't change them.

Also, understand that Visual Studio custom actions happen after the installation, not before, so by the time you do your checkin a custom action the setup is pretty much finished, and if you abort it then it will roll back. Your choices are leave the behavior as it is, use another tool that has the features you want and build your MSI file with it, or learn enough about the content of an MSI file to post-process it with an MSI editor like Orca.