Category: Information – Products

In the latest of update of Visual Installer 2014 (version 10.0.27) we have included a German language file. So you can now use German text in your setup packages in an easy way.

To choose German language to a setup project you must first open the Special – Language menu item in Visual Installer’s editor. And thereafter you choose the GERMAN.LNG language file in the list that is shown.

Some project specific texts must be entered via the Dialog boxes tab in Visual Installer’s editor, just as before. For example text that you want to show in the Welcome dialog box.

See also
> How do I change language for my setup dialog boxes?
> The ‘Program Files’ folder in different languages (Technical Article)

The Visual Installer installation tool can be used to install and uninstall a Windows service. By combining the XRUN script command with the new script command UNINSTALL_XRUN this is very easy done. UNINSTALL_XRUN is a new script command that vi added to Visual Installer’s scripting language in the version 10.0.27 update of Visual Installer. UNINSTALL_XRUN runs a program during Visual Installer’s uninstallation process.

XRUN can be used to install (register) the Windows service and UNINSTALL_XRUN can be used to uninstall (unregister) the Windows service. In this new tip on our website we will explain in detail how to install and uninstall a Windows service using the scripting language in Visual Installer 2014 / Professional:

> Tip: How to install a Windows service using script

Earlier this year we added the MSIEXEC script command to Visual Installer’s script language. MSIEXEC is used to run an MSI installation from a Visual Installer setup package. Windows Installer is used for the setup process. We have now added a new script command that functions like MSIEXEC but it is run during the uninstallation process instead. The name of the new script command is UNINSTALL_MSIEXEC.

Just like MSIEXEC, the UNINSTALL_MSIEXEC command takes three parameters:

%Filename : Full path to the MSI setup package
%Param : Command line parameters to send to Windows Installer
%Wait : Pause Visual Installer until Windows Installer is ready

By combining MSIEXEC with UNINSTALL_MSIEXEC you will have a nice and easy way to support both installation and uninstallation of a MSI setup package in a single Visual Installer project. The picture below shows how to use these two commands in a Visual Installer project:

As you can see, only two lines with script code is needed to handle both an installation and uninstallation of a MSI setup package. MSI_EXEC is run during the installation process and UNINSTALL_MSIEXEC is run during the uninstallation process.

Tips
We have published tips on our website that explains in detail how to use the MSIEXEC and UNINSTALL_MSIEXEC command. Click on the links below to read the tips:

> Tip: How to run an MSI installation from script
> Tip: How to run an MSI uninstallation from script

We have now released an update of SamLogic Visual Installer 2014 (version 10.0.20) that contains many new functions and improvements. Below are some examples of new functions that we have included in the update of Visual Installer:

– You can now add version information (for example a version number, product name and company name) to a self-extracting setup package. Read more.

– Visual Installer can now register a .NET assembly and add a COM object interface to the assembly, so it can be accessed from unmanaged (native) applications. Read more.

– A new script command with the name MSIEXEC has been added. It can be used to start an MSI installation from Visual installer. Read more.

– A new script command with the name EXIT has been added. It can be used to cancel an installation, for example if some conditions or system requirements are not met.

– A new condition has been included in the scripting language that can be used to check if a specific application or library already has been installed. Read more.

– A new condition has been included in the scripting language that can be used to check if the operating system is 32 bit or 64 bit. Read more.

– Support for Autodesk AutoCAD 2014.

– The OpenSSL library that is used by the Twitter function in Visual Installer has been updated to use the latest version of OpenSSL (version 1.0.1g) which contains a bug fix for the Heartbleed bug. If you use the Twitter function in Visual Installer we recommend you to install the update.

How to download the update
If you have Visual Installer 2014 and a 12 months maintenance plan you can download the update from the following download page:

> Download – Visual Installer 2014 – Latest update

If you have an older version of Visual Installer, for example Visual Installer 2012, you can upgrade to the latest version of Visual Installer from this order page:

> Upgrade to Visual Installer 2014

One new function in Visual Installer 2014 (version 10.0.20, and later) is the possibility to add version information to a self-extracting setup package. You can for example add version number, product name, company name and copyright text. The version information can be seen in Windows Explorer and in other places in Windows.

Where in Visual Installer can the version information be entered?
You can enter the version information in the Version information dialog box in Visual Installer. The dialog box can be opened via the menu item Special – Version information. The picture below shows how the dialog box looks like:

The Version information dialog box has existed in Visual Installer for many years, but what is new is the Save version information also in the self-extracting setup package option in the bottom of the dialog box. This option was added to the dialog box in version 10.0.20 of Visual Installer. If you select this option, the version information that you enter in this dialog box will be stored in the setup package file. If the option is not selected, no version information will be stored in the setup package and the dialog box will function as in previous versions of Visual Installer (for example, as a way to identify installation project files).

The version information can be viewed in Windows Explorer
If you have chosen to add version information to the setup package, the information can be shown in Windows Explorer and other places in Windows. For example, when the mouse pointer is above the filename in Windows Explorer, a tip text with the version information is displayed (as shown in the picture below):

Also the Details tab in the Properties dialog box in Windows Explorer contains this information (the dialog box can be opened by right-clicking on the filename and choosing the Properties menu item). The picture below shows how the information is shown in the Details tab if the text that was entered in this blog post’s first picture is used:

Version number
If you want to add a version number to the setup package, you must use 4 numbers when you specify the version number; for example: 1.2.0.5. Both commas and semicolons are allowed to use as a delimiter. So it is also ok to enter the version number like this: 1,2,0,5.

If you use more than or less than 4 numbers for the version number (for example 1.2) the version number is not stored in the setup package. If you want a version number like this to be stored in the setup package, you can extend the version number with zeros and enter the version number like this: 1.2.0.0.

An ActiveX component must always be registered before use and sometimes also a (native) DLL file must be registered before it can be used. This is very essential in many software projects so Visual Installer have had built-in functions to register ActiveX components and (native) DLL files for many years. In Visual Installer 2014 we have extended this functionality so also a .NET assembly can be registered.

A NET assembly is an application, component or class that is compiled for use with Microsoft .NET Framework. A NET assembly can have an .EXE filename extension or a .DLL filename extension. If the filename extension is .DLL, the assembly is a library assembly and can be used by other .NET code in an easy way. But the assembly can not be used from native (unmanaged) code, unless it is registered in the system and a COM object interface (a COM-callable wrapper) is added to the assembly. The new function that we have added to Visual Installer will make such a registration.

If you add a .NET assembly (with the filename extension .DLL) to Visual Installer’s file list and select the file in the list, a new menu item is added to the List menu. The name of the new menu item is Register .NET assembly (see the picture below):

If you choose this menu item, the following dialog box is shown:

In this dialog box you can set some options that will be used when the .NET assembly is registered, for example which .NET version to use and which bitness (32 bit or 64 bit) to use.

See also
> Visual Installer: Register a .NET assembly
> Tip: How to register a .NET assembly