My install creates an EXE and an MSI. The EXE correctly defaults to the install directory C:\Program Files\MyApp
However, the MSI defaults to the install directory C:\Program Files (x86)\MyApp
Why?
Thanks!
These files are not changed frequently. Maybe every two years we will update.
In the beginning, AI scanned my project and automatically recognized the project references and incorporated them in the install. It sounds like there is no mechanism within AI to re-scan the project for any updates, so ...
I was pretty excited because I found Wizards / Import and thought that would solve my problem. It did bring in the new version (20.1), but it did not remove the obsolete version (19.1) from the AI project (as shown in the Orgranization tab). I can't even seem to delete the 20 or so files from the ...
I updated the Infragistics component of my VB project from version 19.1 to 20.1.
Then I rebuilt it in AI, but it does not update the referenced to the newer DLL's. I know this because when I look at the files under Organization in AI it is still showing the 19.1 components.
I understand I can add a Digital Signature (https://www.advancedinstaller.com/user-guide/digital-signature.html) to my installation.
My question is whether this will get rid of the "Windows protected your PC" prompt for my users. I've been reading that just signing is not enough, that you also need ...
I noticed that my AI version is 16.8 but the VS error references 16.4. So I went into VS Community 2019, Extensions menu, Manage Extensions, deleted Advanced Installer Extension, and then re-added it (version 16.8). I still get the same error.
SetSite failed for package [AdvInstVSIntegrationPackage]Source: 'AdvInstExtensionVSIntegration.vcs16' Description: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=16.4.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one ...
FOLLOW US
Get the latest news in Application Packaging