I tried to just build it in 9.3 but still no good - so I rolled back to before the changes and added them in again in 9.3 and it worked fine in there.. so that is cool.
Does the 9.3 fix allow you to take a 9.2 project which won't build into 9.3 and then build successfully? or is the fix that in 9.3 the corruption won't occur when you are working ai?
I am certainly no expert but I think you can just go to Deployment -> Media and then under Package Type choose "Single Exe setup (resources inside)".
That normally does the trick for me when I just want an "exe" only.
Ok - don't worry about this one guys... I had another think about it this morning and I added in a deferred with no impersonation custom action to look after the values..
Basically set it to run on Maintenance only - detects if a component of Feature2 is not installed... (eg. $mycompfromfeature2 ...
I am having a little trouble with a files getting removed when modifying what features are installed. I am using Enterprise edition 9.2.
Basically I have an MSI with multiple features. FEATURE A, FEATURE B and FEATURE C. FEATURE A and FEATURE C actually install some of the same files in ...
I can't seem to find a link on the net ... with the change over from Business Objects to SAP its hard to find any links on the SAP site now - I will send it through to the support email. Thanks!
Hi there. I am using Advanced installer 9.2 Enterprise edition.
I am currently creating an installer where I am including an MSI as a chained package. This MSI requires elevated rights as does the main MSI that I am chaining it to.
If I run the installer it will prompt for elevated rights and then ...
I am having some troubles with an MSI that has been created under enterprise 7.6.1 of Advanced Installer.
The problem is when installing on a machine where the user's My Document's folder is not available at the time of running the MSI and it fails as it can't locate the folder.
Hi there, I am using Advanced Installer Enterprise 8.2.
I have a project which includes the creation of a user and group as part of the install. I have a property to store the password (lets call it myProperty) and it is set to ".". I have a dialog to set this.
My custom action is fine in that I can see from the msi log that the value gets set, it is just that it gets set back again to the property set by the previous Property set with Formatted custom action. So was a bit weird.
So my question really is -> is that sequence that I outlined ...
FOLLOW US
Get the latest news in Application Packaging