You can now choose which shortcut to feature in the Start menu

If you add more than one shortcut to the Start menu in Windows during an installation, and one of the shortcuts is used to open your main application and the other shortcuts are used to open extra tools (when needed), you can now let Visual Installer inform Windows which of the shortcuts that opens your main application.

The shortcut to the main application will be more visible in the Start menu and the other shortcuts will be toned down. By using this new function in Visual Installer you will also eliminate the risk that wrong program is featured in the Start menu. This is a risk if you let Windows itself decide which program(s) that are the most important in your installation. Sometimes Windows makes a wrong guess here.

This is a new function in Visual Installer 2022 and is located in the Program group / menu dialog box in Visual Installer’s editor. A combobox with a list of all program files with shortcuts in the current installation project will be available in the dialog box. From the combobox you can choose which program is your installation’s main program. See the picture below for an example:

The 'Program Group' dialog box

The picture above shows the settings in the installation project for installation of our product MultiMailer 2022. The program file MultMail.exe has been selected as the installation’s main program. The other program files are tools that are seldom used, but they will be in the Start menu in a program group folder, and used when needed.

This new function is especially useful in Windows 11, where recently added shortcuts are featured in an extra clear way. For an example, see below:

Windows 11 Start menu - With MultiMailer

The example above shows how MultiMailer 2022 is featured in the Start menu in Windows 11. The other shortcuts in the installation project are not visible here. Instead they are visible if you click on the All apps button (in the upper right) and opens the program group folder (named SamLogic MultiMailer).

This function will also be useful in older Windows. Recently added shortcuts are featured also there, but in a different way compared with Windows 11.

Visual Installer now display filenames for files being registered during an installation

The installer in Visual Installer now displays the filename of every file that is registered during the registration process. If you have many files in your file list that need to be registered it may take some time in some computers, especially in slow computers, but by displaying the filenames one by one, the user can see that the installation still proceeds.

Registration process

This is a new feature in Visual Installer 2022 and can be turned on and off for each installation project. If you want to turn this function off for a project, you can do it by choosing the Setup options menu item in the Special menu, and clicking on the Various tab and then removing the check mark from the Display filenames for files that are registered checkbox.

As default this option is automatically turned on for your projects.

How to test if Microsoft Access or Microsoft Excel is installed

Logotypes - Access and ExcelIn this blog post we described how to check if Microsoft Office is installed in a computer during an installation. But what if Microsoft Word and Microsoft PowerPoint is installed, but not Microsoft Access, which is what you want? How to handle this situation in Visual Installer?

In the new Visual Installer 2022 the answer is to use a new script condition that we have added to the script language. The name of the new script condition is IF ACCESS_INSTALLED and with this script condition you can check if Microsoft Access specifically has been installed in the computer. So instead of trying to use the Microsoft Office condition check (as described in the earlier blog post) you can use the new Microsoft Access condition check instead.

Below we show two examples of how to use the new condition:

// Example 1 – Tests if Microsoft Access is installed in the system
IF ACCESS_INSTALLED
  RUN %DESTDIR\InstallAccessTools.exe
END IF
 
// Example 2 – Tests if Microsoft Access is not installed in the system
IF NOT ACCESS_INSTALLED
  MSGBOX “Information”, “Microsoft Access is not installed in this computer!”, 2
END IF

 
You can also test if Microsoft Excel has been installed or not in the same way. Below we show two examples of how to use the Excel condition:

// Example 1 – Tests if Microsoft Excel is installed in the system
IF EXCEL_INSTALLED
  RUN %DESTDIR\InstallExcelTools.exe
END IF
 
// Example 2 – Tests if Microsoft Excel is not installed in the system
IF NOT EXCEL_INSTALLED
  MSGBOX “Information”, “Microsoft Excel is not installed in this computer!”, 2
END IF

 
It is also useful to know if the user has installed a 32 bit or 64 bit version of the Office program. But here you can use the same condition in Visual Installer’s script language as before (see the second half of this blog post for details).

SamLogic’s Newsletter Issues in 2021

We have an international newsletter that is targeted for our international customers where we publish information and news related to our products and our company. We send the newsletter about 5-7 times/year. In the newsletter you can read about:

– Information about SamLogic Software’s products
– Tips and tricks for SamLogic Software’s programs
– Technical and non-technical articles
– Videos (tip videos and information videos etc.)
– Special offers

Below you can view all newsletter issues that we sent during 2021:

> 05/2021 – FAQ about folders in Visual Installer
> 04/2021 – Button tips for our menu creator tools & a FAQ about titles in Visual Installer
> 03/2021 – Visual Installer can install AutoCAD profiles
> 02/2021 – How to use Visual Installer together with Access
> 01/2021 – Top Lists 2020 – Most read articles, read blog posts and viewed videos

Subscribe to our newsletter
If you want to subscribe to our newsletter you can visit the web page below:
> Subscribe to SamLogic Software’s newsletter

SamLogic now uses a digital certificate from Sectigo for its software

Green lockCode signed binary files (for example .EXE and .DLL files) are very important to keep a high security level and prevent any attempts to tamper with the binary files after distribution. For that reason SamLogic has code signed its binary files for years now.

We have now updated our digital certificate to use a RSA key length of 4096 bits for the encryption of the certificate. Previous we used 2048 bits. Computers are getting faster and faster (this includes the computers that are used to crack encryptions) and to continue to keep a high security level, it is necessary to increase the key length with time.

Sectigo LogotypeStarting from today we will use an Extended Validation (EV) Code Signing certificate from Sectigo with a key length of 4096 bits for the RSA encryption of the digital certificate. We will use it to digital sign all binary files (.EXE/.DLL/.OCX files) that we release and distribute. In the new 2022 versions of our software, that we soon release, all binary files will be digitally signed with this new and more secure digital certificate.

More information about code signing and digital certificates
If you want to read more about code signing and digital certificates, we recommend the following articles and blog posts on our website:

> What is Code Signing / Digital Signature / Digital Certificate?
> Extended Validation (EV) Code Signing in Windows
> Visual Installer now supports EV code signing

How to run a program with correct bitness (from Visual Installer)

Symbolic image: 32 / 64 bitAssume that you have 64 bit version of a program that you want to be run in 64 bit Windows and a 32 bit version of a the same program that you want to be run in 32 bit Windows only. How do you do that from Visual Installer?

That is easy. Use conditional script.

Below we show how the script lines may look like:

// Run only in 32 bit Windows
IF OSBIT=32
  RUN %DESTDIR\App32.exe
END IF
 
// Run only in 64 bit Windows
IF OSBIT=64
  RUN %DESTDIR\App64.exe
END IF

   
You can use the same method to run an external installation package with a specific bitness. For example a 32 bit installation package in 32 bit Windows only and a 64 bit installation package in 64 bit Windows only.

See also:
> Visual Installer’s Scripting Language
> How to check bitness for an .EXE, .DLL or .OCX file
> How to install a 64 bit program

How to configure the Visual Installer editor

Visual Installer’s editor and user interface is configurable to some degree. If you choose the Special – Editor options menu option in Visual Installer’s editor, a dialog box with the title Editor Options is opened (see the pictures below):

The Editor options menu option

The Editor Options dialog box

The Editor Options dialog box contains various settings that can be used to change the behavior and visual appearance for Visual Installer’s editor. The settings are located in five different tabs in the dialog box (Editor, Tabs, Compression, Miscellaneous, Font), and in this blog post we will describe the settings in these tabs closer.

Tab: “Editor”
Via this tab you can change some common options for the editor that affects the visual appearance of the editor. The tab contains the following options:
 Show source file paths in the file list: If selected, source file paths are show in the file list.
 Show comments in the file list: If selected, comments are show in the file list. Read more.
 Show grid lines in the file list: If selected, grid lines are show in the file list.
 Update file list automatically: If selected, date, size etc. are retrieved when file list is opened.
 Show start window: If selected, the start window is shown when the editor starts.
 Application window’s style: Here you can select a visual style for the editor. Read more.
 Button style: Here you chose a style for the buttons in Visual Installer’s editor.

Tab: “Tabs”
Via this tab you can show or hide some of the main tabs in the Visual Installer editor. So if there is a main tab that you never use (for example the INI files tab) you can hide it in the editor. You can show/hide the following tabs: Registry, INI files, Components. Read more.

Main tabs in Visual Installer

Tab: “Compression”
Via this tab you can set some advanced options that affects the compression of created setup files. Normally the default values will do a good job, but if you want to change some options, you can do it in this tab.

Tab: “Miscellaneous”
Via this tab you can set some various options. You can for example change the default folder for your installation project files. Read more.

Tab: “Font”
Via this tab you can change the font for the editor. Read more in this blog post.

See also
> Information and tips pages: “Tips & tricks for SamLogic Visual Installer”

How to display a text message during an installation

It is possible to display a text message during an installation (that is created with Visual Installer). You can do it via Visual Installer’s script language. There are two commands available for this purpose:

MESSAGE : Displays a text message on the progress bar window.
MSGBOX : Shows a message box with a title, text and an OK button.

If you use the MESSAGE command, the text will be shown until another text need to be displayed or the progress bar is closed. If you use the MSGBOX command, the installation will pause until the end-user click the OK button in the message box.

MESSAGE
Below is an example of how to use the MESSAGE command:

MESSAGE My MSI installation is running
MSIEXEC %DESTDIR\MySetup.msi, /qn, WAIT

   
MSGBOX
Below is an example of how to use the MSGBOX command:

IF NOT OFFICEINSTALLED
  MSGBOX Information, There is no MS Office installed in this computer! , 2
  EXIT
END IF

   
MSGBOXThe picture to the right shows how the message box created in the scripting code example above will look like when shown during an installation. When the end-user clicks on the OK button, the installation continues to the next script line, where the EXIT command halts the installation.

More information
More information about the commands described above is available in Visual Installer´s Help Documentation and User´s Guide. General information about Visual Installer’s script language can be found on this web page.

FAQ about destination folders for EXE, DLL & OCX files in Visual Installer

FAQThere are some common questions about destination folders for binary files (EXE, DLL, OCX files etc.) in Visual Installer that we sometimes get asked from our customers. You will find the questions & answers below, and if you are new to Visual Installer we recommend you to read them:

Questions and answers:


#1
Q: Should I use the C:\Program Files folder or the C:\Program Files (x86) folder as a destination for my application file?

A: It depends of the bitness of your application. 32 bit applications should be installed to the Program Files (x86) folder and 64 bit applications to the Program Files folder.

However, Visual Installer will choose correct folder automatically for you, if you specify your application’s bitness in the 32/64 bit tab in the Setup options dialog box in Visual Installer.

The Setup options dialog box

You can open this dialog box by choosing the Setup options menu item in the Special menu.


#2
Q: How do I do in Visual Installer to install a file to the program files folder?

A: Installing a file to the program files folder (the Program Files or the Program Files (x86) folder) is easy done in Visual Installer, but you need to specify the settings for this in two steps:

Step one:
1. Open the File list tab in Visual Installer’s editor.
2. Click on the […] button to the right of the Main folder text box in the tab (it is located in the upper right part of the editor window).
3. Select the %PROGRAMFILES option in the dialog box that is shown (see the picture below).

The Main Folder Variable Suggestions dialog box

4. Click the Select button.
5. Add (enter) a sub folder name after the %PROGRAMFILES variable in the Main folder text box. Below is an example:

Main folder

You have now specified the main destination folder for your installation. In the next step we will specify the destination folder for the specific file that you want to install.

Step two:
1. Choose the List – Add – Add files menu item in Visual Installer’s editor.
2. Select your file in the Add files dialog box.
3. Confirm that the text after the Folder text box is %DESTDIR in the following dialog box:

The Destination folder dialog box (1)

4. Click the OK button.

Now this file will be installed to the Program Files or the Program Files (x86) folder during the installation. If your application is a 32 bit application, the Program Files (x86) folder will be used as a destination. You can read more in this blog post and in this tip.


#3
Q: How do I install a file to the system folder?

A: If you have for example a DLL or OCX file that need to be installed to Windows’ system folder it can be done in Visual Installer. Follow the instructions below to do it:

1. Open the File list tab in Visual Installer’s editor.
2. Choose the List – Add – Add files menu item in Visual Installer’s editor.
3. Select your file in the Add files dialog box.
4. Select the System directory option in the following dialog box:

The Destination folder dialog box (2)

5. Click the OK button.

Now this file will be installed to Window’s system folder during the installation. The exact folder that is used depends of your installation project’s bitness (see question 1 above).


#4
Q: In some dialog boxes and other places in Visual Installer’s editor I see words like %PROGRAMFILES, %DESTDIR and %SYSDIR etc. What are they?

A: %PROGRAMFILES, %DESTDIR and %SYSDIR etc. are called variables. The name of the variable will be replaced with an actual text during the installation.

Variables are used when the actual text is not known, until the installation starts. Variables are usually used as a place holder for folder paths. For example the %PROGRAMFILES variable is a place holder for the program files folder in the system. When the installation starts, %PROGRAMFILES is replaced with the actual folder path. For example with C:\Program Files.

You can read more about variables in this blog post.


#5
Q: I have an international application. The name of the program files folder is different in different countries / languages. Can Visual Installer handle this?

A: Yes. Visual Installer will find the correct path to the program files folder regardless of country / language or version of Windows. You can read more in this blog post.

More information
If you want more information about the settings in the dialog boxes above, you can press the F1 button on your keyboard when the dialog box is open. We recommend you also to take a look on Visual Installer’s tips and tricks pages:

> Tips & tricks for SamLogic Visual Installer