Install Shield 2015 Documentation

C#

What’s Installshield?

InstallShield is a proprietary software tool for creating installers or software packages. InstallShield is primarily used for installing software for Microsoft Windows desktop and server platforms, though it can also be used to manage software applications and packages on a variety of handheld and mobile devices.  

How to create installations software?

If you have ever installed an application onto your computer, you have seen an installation in action—from the end user’s perspective. An installation’s primary task is to transfer files from the source medium to the local drive. An installation often also displays a user interface to obtain end user selections, configures the target system (for example, makes any required registry entries and creates shortcuts), and enables modification or uninstallation of the installed application.

Creating an installation involves performing some or all of the following tasks. 

I.Specify Installation Information

Basic information that you enter in the General Information view is used in various parts of the installation; for example, the product name is used to create the application information registry key.

II.Organize and Transfer Files(Important module)

File transfer involves copying files from the source medium, such as a CD or DVD, to a local drive on the end user’s machine. Depending on the configuration the end user chooses—by selecting a setup type (in an InstallScript or InstallScript MSI installation) or features—all or only some of the files may be transferred to the local disk.

Organize the files to be installed into setup types and features to help your end users select the most appropriate files. Within each feature, organize the files into components according to their type and purpose, for example, files that are installed to the same target folder.

Special point:

 1.Setup

Allow user design project structure like (default component,DllFile,Font,Language,Report , etc….)

note : all setup design just a design view(easy manage),but installation directory it will follow property  [Destination].

 1.1.Feature & Components

Allow user add all requirement file that we have to use in system.

after added all component that we want to use in system we have to create associate component with feature.

To create associate between feature and component

note : In the property the row Destination : The location of component

example : Font : Destination = [FontsFolder] not in [[INSTALLDIR]]

 2.Application Data

Requirement file that we need to include to the system or if the system required to use redistributable such as (Window Instaler, Dotnet framwork 3.5, or any redistributable we can include that here).

2.1.Adding System file

2.2Adding Redistributable

After add redistributable it will download if it still its not local file .

Redistributable Property

+ Copy From Source Media : It will create folder ISSetupPrerequisites that include that redistributable file

so when the user setup it will extract file from that directory.

+ Download From The Web : It will required user download that redistributable file from the web.

+ Extract From Setup : It will include redistributable file to the exe file(exe file will be high size).

III. System Configuration

In addition to installing files, many installations need to configure the target system by creating shortcuts and program folders, modifying the registry, modifying initialization file (.ini file) data, configuring Open Database Connectivity (ODBC) resources, modifying environment variables, modifying XML files, modifying text files, schedule tasks, and install and control Windows services.

note : to create shortcuts and make sure it will run correct directory we need to configure working directory to [INSTALLDIR].

IV. Server Configuration

A server-side installation may need to create and manage new Internet Information Services (IIS) Web sites, manage COM+ applications and components, or manage and organize SQL scripts by server connections and settings.

V. Behavior and Logic 

InstallShield offers wide-ranging customization options. InstallScript installations are driven by InstallShield’s simple but powerful InstallScript programming language, which—in addition to its built-in functions—enables you to call DLL and Windows API functions and launch child installations and other applications from your installation. Windows Installer-based installations can use custom actions to run InstallScript, VBScript, or JavaScript code; call DLL functions; run executable files; call a managed method in a managed assembly; set a property or a directory; trigger an error and end the installation; run PowerShell scripts; terminate a process; or run other installation packages.

VI. User Interface

An installation’s end-user interface provides information and installation configuration options to the end user. Through the user interface, an end user can choose to install only part of a product, choose to leave some files on the source medium, view a license agreement, or provide the installer information that may be necessary to properly configure the installation.

The user interface can be customized to meet the needs of your installation. For example, you can prompt a user for a serial number before starting the installation to protect your software against illegal use. During file transfer, an installation can display billboards that provide product information such as new features or usability tips. A status bar may also be displayed to show the progress of the file transfer process.

VI. Media

Once you have created your installation project, you will want to build, test, and deploy the installation: create the files that you will release to your users, test the installation for errors, and optionally copy the files to a local or network location or an FTP site.

———- Other document and reference —————–

 

Leave a Reply

Your email address will not be published. Required fields are marked *