We're considering purchasing Advanced Installer to deploy a .NET / SQL application & updates.
How clever is the SQL script deployment? OUr ideal setup is:
1) Trigger scripts to be run at the start of the installation package
2) Dynamically determine which scripts need to run based on versioning data within the database
3) Rollback all scripts & halt software installation if any error occurs
4) Trigger a database backup before any scripts are run
If Advanced Installer can't do all these things, I assume it is able to trigger a custom .NET DLL we create, then halt it's own execution depending on the response code?
Regards,
-Brendan
FOLLOW US
Get the latest news in Application Packaging