I found that my application behave different when executed from installer and after exit setup. After investigation I found issue partly in Windows.
I have prerequisite SQL Server. When application is first time executed there are scripts to run. For executing scripts we use osql/sqlcmd.
Option 1) Application is installed and user close setup. Then run application shortcut and everything is working perfecly
Option 2) Application is installed and user Run application from setup. Scripts can't be executed !!! (osql/sqlcmd is not found)
Issue is environment variables (PATH). In Windows variables are read when process starts. When I run application directly from setup %PATH% value is without changes applied by SQL Server installation. I was surprised "Launch application at the end of installation" does not behave same like launch application by shortcut. I think this should start new process and not continue in existing one (idea: send system message to execute application and then close setup). Because I don't know how it works internally could you give me some workaround ideas. Have a possibility to run application immediately from setup is recommended for our users because we have same essential functionality integrated in application.
FOLLOW US
Get the latest news in Application Packaging