Revise Your Events Seamlessly: Mastering the Edit Event Feature

Table of Contents

• Introduction
• Registration
• Using Advanced Installer
  • GUI
  • Working with Projects
  • Installer Project
    * Product Information
    * Resources
    * Package Definition
    * Install Parameters
    * Organization
    * Builds
    * Configuration Tab
    * Advanced Media Tab
    * Mac OS X Tab
    * App-V 4.x Tab
    * App-V 5.x Tab
    * ThinApp Tab
    * Configuration Tab
    * App Installer Tab
    * UWP Bootstrapper Tab
    * Build Events Tab
    * Edit Event Dialog
    * Add a command-line batch file as a custom event
    * Add a VBScript file as a custom event
    * Add an executable file as a custom event
    * Powershell build event
    * Optional Package Tab
    * Symbol Files Tab
    * Analytics
    * SCCM
    * ActiveSync
    * Requirements
    * User Interface
    * System Changes
    * Server
    * Custom Behavior
  • Patch Project
  • Merge Module Project
  • Updates Configuration Project
  • Windows Store App Project
  • Modification Package Project
  • Optional Package Project
  • Windows Mobile CAB Projects
  • Visual Studio Extension Project
  • Software Installer Wizards - Advanced Installer
  • Visual Studio integration
  • Alternative to AdminStudio/Wise
  • Replace Wise
  • Migrating from Visual Studio Installer
  • Keyboard Shortcuts
  • Shell Integration
  • Command Line
  • Advanced Installer PowerShell Automation Interfaces
• Features and Functionality
• Tutorials
• Samples
• How-tos
• FAQs
• Windows Installer
• Deployment Technologies
• IT Pro
• MSIX
• Video Tutorials
• Advanced Installer Blog
• Table of Contents

Disclaimer: This post includes affiliate links

If you click on a link and make a purchase, I may receive a commission at no extra cost to you.

Edit Event Dialog

In this dialog, you can add a new event, or you can edit an existing one for the selected build.

Application

Command

The command to run. Use [… ] button to browse for an external file. This field is of PseudoFormatted Type and can be edited using Smart Edit Control .

Click here

Arguments

Specify arguments for the command to run. This field is ofPseudoFormatted Type and can be edited usingSmart Edit Control .

It is important to enclose the paths in quotation marks (“ “) otherwise the operations might not be executed correctly or will return an error code. This usually happens when the folder, file name contains spaces or more than 8 characters.

Working Dir

Specify working directory for the command to run. This field is of PseudoFormatted Type and can be edited using Smart Edit Control .

Redirect output

Specify the full path of the file where you want the output of the executed application to be redirected. This field is of PseudoFormatted Type and can be edited using Smart Edit Control .

Build

Log Description

Specify the text showed in the build log when the event is executed. This field is of PseudoFormatted Type and can be edited using Smart Edit Control .

Execute this before EXE packing

If this option is enabled the event will be executed before the MSI package will be inserted into the final EXE file. This option makes sense only if the Create EXE setup file option is enabled in the Configuration Tab ; otherwise, it will act as a normal Post-Build event.

This option can be used only for Post-Build Events, because this is the only moment when an event can be scheduledafter the creation of the MSI file andbefore the EXE file is generated.

Cancel build in case of a launch failure

Enable this option for the build process to be interrupted if the specified command returns with an error.

Execute only if build failed

This option ensures the execution of the post-build event only in case the build failed.

Did you find this page useful?

Please give it a rating:

Thanks!

Report a problem on this page

Information is incorrect or missing

Information is unclear or confusing

Something else

Can you tell us what’s wrong?

Send message

Also read: