Sooner of later most SAAS applications find they need to integrate with Microsoft’s ecosystem to satisfy their customer’s needs. This post looks at the four technologies which are available to integrate with Microsoft Outlook, Exchange, and Office 365, and starts to examine when each might be used.
We were recently asked to change the icon showing in Outlook for messages when they had been filed to a CRM system.
The image below shows an example of the icons in Outlook. The top message has been forwarded and shows the icon for a forwarded message. The second message is a copy of the first, but the icon has been changed to one of the standard icons.
It is possible to set the icon to one of the many pre-defined icons within Outlook. The full list of icons is shown below.
In order to change the icon, the field PR_ICON_INDEX must be programatically set to the value of the required icon.
This way, when a user has carried out a particular action on a message, the message icon can be changed so that the user knows it has been completed.
It is often desirable for an installer to be provided with specific data at the time of the installation. For example to supply a user name, password, license string etc. Passing command line arguments while initiating the installation process allows us to do this. This article gives you a detailed description about how to pass data to custom actions in a WIX Installer using command line arguments.
Why use Custom Actions?
The installer provides many standard actions that execute during an installation. However, there may be times where your installation needs expanded functionality. In these cases, custom actions let you extend the capabilities of standard actions. We can use custom actions for the following scenarios.
- Launch an executable during installation that is installed on the user’s machine or that is being installed with the application.
- Call special functions during an installation that are defined in a – (DLL).
- Use functions written in the development languages Microsoft Visual Basic Scripting Edition or Microsoft JScript literal script text during an installation.
- Defer the execution of some actions until the time when the installation script is being executed.
- Add time and progress information to a ProgressBar control and a TimeRemaining Text control.
Creating a sample project.
In this sample project, we tell the Wix Installer to use custom actions to execute an .msi with command line arguments. The example will create a sample installer for a Windows Form Application.
Start Visual Studio and go to “File->New Project” under the installed section select Windows Forms Application [Figure1].
Create an Installer for the application
Right click on the solution and “Add->New Project“. Under Wix Toolset select Setup Project and add a new one. To install Wix Toolset, go to http://wixtoolset.org/releases/ download, setup and install [Figure2].
In the CustomActionSetup project, right-click on the References node and choose Add Reference.
Navigate to the Projects tab, click on the SampleApp project, and click the Add button, and then press OK [Figure3].
Create a Custom Action for the application.
Once we’ve created our setup project, we’ll need to add a C# Custom Action Project to our solution (you can see this project template option in the below screenshot as well).
To create a custom action, right click on the solution and “Add->New Project“. Under Wix Toolset select a “C# Custom Action Project” and add a new one [Figure 4].
Here is the final Solution [Figure 5].
Edit Product.wxs in Wix Setup Project
After creating the setup project you’ll have a Product.wxs file that defines your setup. In the Product.wxs file, we can define custom actions and properties which are sent through the command line.
- Define two properties “LIC” and “NAME”. See more on the Property Element in Wix here:
- Binary tag a link to the DLL. Here you will need to give a source location for the dll with any unique ID value. When we build the installer, a custom action project (.CA.dll) is created in the bin folder.
- In the CustomAction tag, you need to define which custom action you are using. In here refer to the “GetArguementValues” custom action and add the Binary Id to the BinaryKey property.
- After that define the InstallExecuteSequence for a given custom action. Here specify in which step of the installation the custom action should be executed. See more on the InstallExecuteSequence here:
The screenshot below shows the location of these elements in the Product.wix file [Figure 6]
Within the custom action project, you’ll have a new CustomActions class. In the CustomActions class define a method “GetArguementValues” which we have previously added to the “DllEntry” property in the product.wxs file. Here we get a “LIC” and “NAME” property through a Session object. A custom action can interact with an installing package through “Session objects”. The Session object controls the installation process by opening the installer, which contains the installation data. Finally show in a message box with two parameters [Figure 7].
Pass Command Line Arguments to Wix Installer
You’ve most likely run .msi files simply by double-clicking them from Windows Explorer. However,you can also run an .msi file by typing the file name at the command line. The advantage of running from the command line is that you can pass parameters to the command.
Open a command prompt and ‘Run as administrator’. Figure . To do this click the start button on Windows and search cmd, right click on command prompt and ‘Run as Administrator.
Using command line, we can run the .msi installer and pass parameter values which we define d in the Product.wxs. First go to the location where the .msi file is saved. For this example it’s located in “C:\pro”. Then, using the command msiexec /i CustomActionSetUp.msi LIC=”xxxxxxxxxx” NAME=”davton”, as shown below, you can run the installer and pass the parameter values [Figure 9].
When executing the command, it will open the install wizard and show the message box with the two property values being passed in the command line [Figure 10].
This article provides information for creating a custom action in Wix, passing parameters to custom action functions and extracting parameters passed from an installer inside a custom action function.
Written by Tharaka Pathirana May 2017