Dear Halim, The approach you took should work, but there are some cases when "Launch file" custom action can cause setbacks on running certain command lines. To debug in this direction we would need the installation log but it could very well lead to a dead end. Instead I would recommend you to use ...
From what I know the last certificate used to sign the EXE will be used to verify the package (in your case that will the correct one from your manager). All other files inside the EXE will be signed using the test certificate.
Dear Halim, Welcome to Advanced Installer forums. I looked into your project but I couldn't find any "Launch EXE with working directoy" custom action that attempts an SQL file import so I can review its settings. Did you attach the correct project file? A quick observation after looking into your pr...
You can try to sign the EXE installer with a test certificate at build time by using the Digital Signature page. After this, you can send it to your manager so he can sign the built EXE using the real certificate using any signing tool. Normally, this should work fine.
Does this manifest on all machines, even clean ones? If so can you send us the project file (AIP) and built installer to support at advancedinstaller dot com so we can investigate your settings?
Hello, Yes, it seems the condition for serial validation and another "Show only if" option for dialogs that could help in a similar way, are only available starting with Enterprise. Generally, advanced dialog customizations can be done using the Dialog Editor that comes with Enterprise All the best,...
Dear Jakub, Indeed, those are the properties associated with the controls from the UserRegistrationDlg. To condition when the UserRegistrationDlg is shown, go to Licensing page -> Package Serial Validation section -> Condition section on the bottom. For example by setting: NOT PIDKEY ... the dialog ...
Dear Kietvta, The error is shown from the "SetProperty" custom action. As indicated in the article, you have to set MY_DIR property to [WindowsVolume] instead of WindowsVolume . This is because the "Value" field is formatted and the correct way to reference installer properties is between straight b...
Hi Frank, To prevent a file from being overwritten in an upgrading installer project you could enable its " Do not overwrite existing file " option with OLDPRODUCTS condition from the Files and Folders Page. Read more in the How do I prevent a file or registry entry from being uninstalled or repaire...
Dear Diego, Please note that this condition: 1=1 OR AI_DETECTED_DOTNET_VERSION ...will always evaluate to true. Also, as a side note FYI: AI_DETECTED_DOTNET_VERSION property can be used in any condition field from the project. It doesn't necessarily have to be a launch condition. As long as the prop...
Hello Kietvta, Depending on the data provider, you can configure SQL Server CE connection strings as indicated here: SQL Server Compact connection strings To do this you can still use a custom connection type, but instead of the standard SQL connection string, try one from the article linked above. ...
Hello, We built and tested your installer on a Windows Server 2008 R2 machine but unfortunately we didn't get any error. Does this happen on other (clean) machines? This error usually occurs when the folder path used in the msiexec log command line doesn't exist on the target machine. The /L*V argum...