Original author(s) | Viresh Bhatia and Rick Harold |
---|---|
Developer(s) | Flexera Software |
Stable release | 2019 / April 18, 2019; 16 months ago |
Operating system | Microsoft Windows |
Type | Setup creator |
License | Shareware |
Website | installshield.com |
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.
Features[edit]
Building InstallShield projects via Docker Container. Considering that you already have a Docker image with InstallShield or you are using the Docker image provided by InstallShield. Run the following command to create a container and mount directory in an interactive process; docker run -it -v ':'. Building InstallShield projects via Docker Container. Considering that you already have a Docker image with InstallShield or you are using the Docker image provided by InstallShield. Run the following command to create a container and mount directory in an interactive process; docker run -it -v ':'. Looking for online definition of InstallShield or what InstallShield stands for? InstallShield is listed in the World's largest and most authoritative dictionary database of abbreviations and acronyms. InstallShield - What does InstallShield stand for? The Free Dictionary.
InstallShield generates a .msi file which can be used on the destination computer in order to install the payloads from the source computer where it was created.It is possible to specify questions, set prerequisites and registry settings that the user will be able to choose at the installation time.
Development[edit]
InstallShield was originally developed by The Stirling Group, a company founded in 1987 by Viresh Bhatia and Rick Harold, who had first met when they were computer science students at Northwestern University. Their first office was a small room in the basement of an old library building in Roselle, Illinois. They were to market a geographic mapping software, but it was never released.[1] By 1990, The Stirling Group was selling a package of six products called the Shield Series.[2] In that same year, the company also released the InstallShield product to developers.[3][4]
Commview for wifi wep crack tutorial. In 1993, The Stirling Group moved into larger offices in Schaumburg, Illinois and changed the companies name to Stirling Technologies, Inc. InstallShield became particularly well known after Microsoft endorsed it for use in Windows 95, and by 1997 Stirling Technologies estimated that it was being used in 85 to 90 percent of all software products written for Windows.[3][4] Since 1996, the company operated under the InstallShield name until Macrovision acquired the business in 2004 for $76 million in cash plus an additional $20 million based on meeting sales targets.[5]
Limited versions of InstallShield were at various times bundled with popular software development packages such as Microsoft Visual Studio 6.0, Borland Delphi 2006, and Borland C++Builder.[citation needed]
On 1 April 2008, the Macrovision Software Business Unit (including the InstallShield brand) was sold to private equity firm Thoma Cressey Bravo, forming a new company called Acresso Software.[6] In October 2009, Acresso Software changed its name to Flexera Software.[7]
In May 2020, Flexera Rebranded its Division Serving Software and IoT Companies to Revenera.[8]
See also[edit]
References[edit]
- ^'The Stirling Group'. The Electronic Developer Magazine for OS/2. Archived from the original on 11 September 2016. Retrieved 29 August 2016.
- ^Mann, Leslie (1 March 1998). 'Meet The Original Installshield Wizards'. Chicago Tribune. Archived from the original on 9 August 2016. Retrieved 21 November 2019.
- ^ abSchmitt, Anne (5 November 1997). 'Schaumburg Company makes it possible to open windows'. Daily Herald. p. 40. Archived from the original on 12 August 2016. Retrieved 17 June 2016 – via Newspapers.com.
- ^ abSchmitt, Anne (5 November 1997). 'Schaumburg Company makes it possible to open windows'. Daily Herald. p. 41. Archived from the original on 13 August 2016. Retrieved 17 June 2016 – via Newspapers.com.
- ^Rose, Barbara (18 June 2004). 'Software installer may fetch $96 million'. Chicago Tribune. Archived from the original on 18 August 2017. Retrieved 17 August 2017.
- ^'Thoma Bravo Completes Acquisition of Macrovision's Software Business Unit'. Flexera Software. 1 April 2008. Archived from the original on 18 August 2017. Retrieved 17 August 2017.
- ^Lai, Eric (9 October 2009). 'Acresso who? Macrovision spinoff changes name, again'. Computerworld. Archived from the original on 18 August 2017. Retrieved 17 August 2017.
- ^'Introducing Revenera: Flexera Rebrands Its Division Serving Software and IoT Companies'. 28 May 2020.
External links[edit]
- Official website
Install Shield 2020
Retrieved from 'https://en.wikipedia.org/w/index.php?title=InstallShield&oldid=974628344'
If your organization has purchased concurrent licenses of InstallShield, InstallShield Collaboration, or the Standalone Build, a FlexNet Licensing Server that you set up in your environment manages how many instances of the product can be run simultaneously. Each user who wants to launch one of these products needs to establish a connection with the licensing server to check out and check in licenses when needed.
Connecting a User's Machine to the License Server for Checking Out and Checking In Licenses of InstallShield and InstallShield Collaboration
Once you or someone in your organization has set up the FlexNet Licensing Server, you need to identify the FlexNet Licensing Server that you are using on the machine where you install InstallShield or InstallShield Collaboration.
To identify the FlexNet Licensing Server for InstallShield or InstallShield Collaboration:
- Launch the product. Before the product starts, the activation wizard opens.
- Select the Configure the product to get license information from a license server option and then click the Next button. The product displays the Specify License Server dialog.
- In the Server box, enter the name or IP address of the license server, or click the Browse button to navigate to the server.
- If the FlexNet Licensing Server that was configured in your environment uses a custom port number, enter the port number in the Port box. In most cases, the port number is left blank.
- Click the Test Connection hyperlink.
Installshield Flexera
The wizard connects your machine with the license server to verify whether your machine can check out and check in a license for the product.
Note: If you want to be able to use your new concurrent license of InstallShield on the same machine that is used to check out a concurrent license of InstallShield 2009 or InstallShield 2008, download the following update and install it on your client machine:
InstallShield 2008 and InstallShield 2009 Concurrent License Update
InstallShield 2008 and InstallShield 2009 Concurrent License Update
Connecting a Machine that Has the Standalone Build to the License Server for Checking Out and Checking In Licenses of the Standalone Build
When you install the Standalone Build, the installation prompts you to identify the FlexNet Licensing Server that will be managing concurrent licenses for the product.
To install the Standalone Build and identify the FlexNet Licensing Server that is managing your organization's concurrent licenses:
- Launch the Standalone Build installation.
- On the License Type dialog, select the Concurrent license option.
- On the License Server and Port dialog, enter the name or IP address of the licensing server. If the FlexNet Licensing Server that was configured in your environment uses a custom port number, enter the port number. In most cases, the port number is left blank. When you are done filling in the settings, click the Test Connection button to verify whether the build machine can check out and check in a license for the Standalone Build.
- Complete the remaining dialogs in the installation.
The installation installs the Standalone Build on your build machine. The installation also creates a file called Server.ini. This file is installed in the System folder in the Standalone Build Program Files folder:
Standalone Build Program Files FolderSystemserver.ini
The Server.ini file should contain the following lines:
Installshield Switches
[FlexNet Publisher Server]
Server=Port@ServerName
In the above example, Port is the port number, if a custom port number is used. In most cases, the port number is omitted. ServerName is the name of the machine that has the FlexNet Licensing Server software.
Install Shield Problems
Note: When you are installing the Standalone Build on a build machine, you can do so without specifying the license server name and port number, as long as you later manually add this information in the server.ini file in the aforementioned directory. The Standalone Build does not run without this information (or without its own node-locked license file).