Advanced Installer Community

burnersk

Hi Catalin, I never have build the actual setup. The setup seems to work, but the "Test script" button does not work when "Per-user only" install type condition applies. PS: I mentioned that the MSI also crashes, this was due to a typo that I have fixed, and then only tested with...

burnersk

Hi Catalin, I just tried it on a different system (hardware, Windows 10 build) and I still can reproduce it. My first assumption was DOS file/folder name length restrictions (e.g. "MyUser~1" vs "MyUserAccount"), but I just have reproduced it without hitting this limitation. Now t...

burnersk

I discover critical errors when trying to use (any) PowerShell custom actions when the application is configured to be installed "Per-User only". See the project file: Your Application.aip I receive the following error: Error calling MSI API: 1627 Method: MsiViewExecute Table: Property. Ex...

burnersk

Using Advanced Installer Professional 16.5, I want to have the output folder of the builds dynamic. To accomplish this, I have entered the following formatted type in the output folder setting: [|AI_AIP_FOLDER]\Builds\[|ProductName]-[|ProductVersion]\[|AI_BUILD_NAME] When I try to save the project, ...

burnersk

This forum is is nice source for information, however it is most annoying having this spammers around. I "monitor" this forum on a daily basis to gain tips and tricks about AI. I also have placed some questions. From my point, it is totally acceptable when a new post of me would be "o...

burnersk

However, if it is non intuitive then the versioning looses a large part of it's purpose. Who remembers to look into reference X to decrypt the versioning? It's to complicated for normal users is my opinion Totally agree with you. However, Microsoft will unlikely (personal opinion: definitely never)...

burnersk

Hello, I experienced the same issue as you do. I came up with the following solution (Example: https://1drv.ms/x/s!AiMl0SSQdgy9kUiiBfGFdsan-N9s ) You may have the following semantic version strings: 1.2.3-alpha.1+1 1.2.3-alpha.2+2 1.2.3-beta.1+3 1.2.3-beta.2+4 1.2.3-rc.1+5 1.2.3-rc.2+6 1.2.3+7 11.22...

burnersk

I have a continues integration (CI) server, which builds AI setups for my applications upon successful (tests are passing, not yet merged) pull requests. I also use supported releases. This means that I support older major/minor releases with bug fixes or back-ported features. The most current build...

burnersk

In order to achieve what you want, you can add your prerequisite as a web-installer prerequisite. For instance, you can go to "Prerequisites" page, select the .NET framework from the list of predefined prerequisites and select "No" when it asks if you whether want to download an...

burnersk

I want to build an web installer for an .NET application. I plan to distribute the .NET Framework redistributable included within my application setup. I have setup .NET Framework as a prerequisite and build the web installer. Unfortunately, the .NET Framework redistributable is moved into the "...

burnersk

I have a AI Professional license and would like to use the "Enter serial number" feature as it is in AI Professional. I have a 3rd party licensing product and do not require or want to use AI Enterprise's licensing feature (3rd party product is by far superior: obfuscation, encryption, flo...

burnersk

I have a AI Professional license and want to use AI's serial validation feature. My application is protected by a commercial 3rd party solution that is build with .NET. So a direct integration from AI to the 3rd party .NET licensing library is not possible. I found this generic solution for standard...

burnersk

Using Advanced Installer Professional v15.8, how to I authoring for a preview/beta release setup? I am using the Semantic Versioning standard for version strings. The following version are in order: 1.0.0-alpha.1+17 (first alpha of 1.0.0, build 17) 1.0.0-alpha.2+21 (second alpha of 1.0.0, build 21) ...

Suggested Articles

User Guide

Videos

Search found 43 matches

Re: Running PowerShell inline script causes errors (1627, 2210) when installed "Per-User only"

Re: Running PowerShell inline script causes errors (1627, 2210) when installed "Per-User only"

Running PowerShell inline script causes errors (1627, 2210) when installed "Per-User only"

Dynamic build output folder

Please enable forum's moderation support

Re: file version vs product version attribute

Re: file version vs product version attribute

Building installers within a CI environment with supported releases

Re: Web installer with prerequisites as individual CABs?

Web installer with prerequisites as individual CABs?

Adding Support for empty serial numbers (unlicensed/trial)

Using .NET DLL for serial validation with CLR/Standard DLL mappers?

Authoring setups for preview/beta releases

Caphyon Products

Company

Product

Resources

Free Tools

Connect