InstallShield

InstallShield is once again revolutionizing software installations with new support for application virtualization with Microsoft® App-V™.

Now when you build a traditional MSI project, InstallShield 2010 can simultaneously build it as a virtual App-V package. It can also automatically modify your legacy MSIs to App-V packages. InstallShield 2010 handles all the conversion work, so there’s no learning curve for developers new to application virtualization.

To an end user, virtual applications appear and function just like physically installed software. But virtual applications never get installed on the client. Instead they run in their own isolated virtual containers – which include registry entries, libraries, executables, and anything else the application needs to run – completely separate from the operating system. Because there’s no physical installation, there are no installation or retirement problems and no application compatibility issues.

InstallShield 2010’s App-V support is ideal for companies adopting application virtualization for their own environments. Virtual formats like App-V are also useful for software vendors offering evaluation versions of their products. Many end users are hesitant to install evaluations because of the potential risk to their machines. With InstallShield 2010, developers can offer evals as virtual packages, eliminating those fears and increasing evaluations.

Microsoft’s release of Windows 7 will be a major event in 2009. Companies reluctant to adopt Windows Vista are expected to make the move to Windows 7, and software vendors will need to make sure their products are compatible with the new OS.

InstallShield 2010 has the tools developers need to get a head start on supporting Windows 7. It makes it easy to create applications that meet Microsoft’s requirements for the “Compatible with Windows 7” logo.

InstallShield 2010 makes it easy to install applications on Windows Server 2008 R2. You can now specify that your installation requires Windows Server 2008 R2 and build conditions for features and components.

Windows Installer 5 is available with the releases of Windows 7 and Windows Server 2008 R2. With InstallShield 2010’s own implementation of Windows Installer 5 features, you can take advantage of the cool new MSI 5 functionality, including:

• Creating per-user applications
• Quicker installations for large packages

InstallShield 2010 enables you to run SQL scripts on SQL Server SP1 (available in InstallShield Premier and Professional Editions only), and includes support for SQL Server Compact Edition 3.5 SP1 for mobile device installations.

Simply put, InstallShield 2010 gives developers the IDE they’ve been asking for. From new toolbars and views to customizable grids to dynamic search tools, this is by far the best user interface InstallShield has ever offered, saving developers a ton of time.

Some of the highlights include:

• Direct Editor view: When you select a table in this view, a new toolbar is displayed for adding, finding, and editing data in the table. (InstallShield 2010 Premier and Professional Editions only)
• Property Manager view: This view contains a new toolbar that has buttons for performing tasks such as adding and deleting properties. You can also drag and drop column headings onto a new group box area to organize the rows in the view in a hierarchical format. (InstallShield Premier and Professional Editions only)
• Redistributables view: The new toolbar and the new group box area in this view provide robust search and organizational functionality.
• Internet Information Services view: This view has been redesigned to look similar to IIS 7, making it much easier to use.
• General Information view: All of the settings in this view are displayed in one grid, instead of as separate grids associated with nodes. The settings are grouped into several categories to make them easier to find.
• Path Variables view: This view contains a new toolbar that has buttons for performing tasks such as adding and deleting path variables. It also has support for dynamic searches and a new group box area for organizing rows in a hierarchical format. (InstallShield Premier and Professional Editions only)

This new view contains a spreadsheet-like table that shows the collection of language-independent identifiers and corresponding language-specific values for your project.

Get complete and centralized control over the localizable text strings that are displayed at run time during the installation process. Some highlights include a toolbar for adding and editing string entries and a group box area for sorting string entries by categories such as language and by modified date.

This new view lets you configure search-and-replace behavior for content in text files (such as .txt, .htm, .xml, .config, .ini, and .sql files) that you want to modify at run time on the target system.

The text files can be part of your installation, or they can be files that are already present on target systems.

Internet Information Services (IIS) is a Web server developed by Microsoft. It provides a secure platform for building and deploying Web-based applications, managing Web sites, and publishing information to the Internet or an intranet.

InstallShield 2010 has significantly improved IIS-related functionality that makes it even easier to create and manage new IIS Web sites, Web applications, virtual directories, application pools, and Web service extensions.

InstallShield 2010 has enhanced its Internet Information Services view to look similar to IIS 7. The settings are now displayed in grids, instead of on tabs. And the grids have buttons that let you sort the grid settings by category or alphabetically. Longtime users of InstallShield will notice and appreciate the difference right away. (Available in InstallShield Premier and Professional Editions only).

InstallShield 2010 now gives developers the ability to add IIS Web applications to IIS Web sites and configure as needed. Plus, you can now create an IIS virtual directory without an application. Both enhancements were popular requests by the InstallShield community.

InstallShield 2010 has a new IIS Scanner that analyzes and records IIS data about a Web site’s settings – including its virtual directories, applications, and application pools – and imports it into the Internet Information Services view. So instead of having to waste time manually entering data, InstallShield 2010 finds it and adds it for you. Developers can then use that view to make any changes to the IIS settings. (Available in InstallShield Premier Edition only).

In addition, InstallShield 2010 Premier and Professional Editions have new IIS settings that our users have specifically requested, including:

• Managed Pipeline Mode: Specify the appropriate request-processing pipeline mode—either integrated or classic—for an application pool.
• Enable 32-Bit Applications: Specify whether you want to allow 32-bit applications in the selected application pool to be run on 64-bit systems.
• .NET Framework Version: Specify the version of the .NET Framework that an application pool should load.
• ASP.NET Platform: For installations that may run on a 64-bit version of Windows with the .NET Framework, specify which ASP.NET platform should be used to map a Web site, application, or virtual directory to the ASP.NET version.

InstallShield 2010 now enables you to add InstallShield prerequisites to your InstallScript projects. InstallShield prerequisites are redistributables that usually install a product or technology framework required by your application.

If you work on a mix of different project types, InstallShield 2010 lets you simplify your testing matrix by enabling you to reuse this type of redistributable in all of your Basic MSI, InstallScript, and InstallScript MSI projects.

Virtual machines have been a licensing and compliance challenge for software vendors. If you don’t want your products to run on virtual machines, InstallShield 2010 has the answer.

It can now build installations that detect when they are being run on virtual machines like Microsoft Hyper-V and Virtual PC or VMware and optionally block the installation.

For applications that run in locked-down environments, InstallShield 2010 has new functionality that significantly improved the way installations set files, folders, and registry keys at run time.

Developers frustrated with the traditional Windows Installer LockPermissions option will appreciate the improvements, none of which are supported by the old option, including:

• Support for many well-known security identifiers (SIDs) such as guest, everyone, and administrator
• Support for localized user names, which could cause the installation to fail in the traditional option
• Denying a user or group from having the permissions you are specifying
• Adding permissions to a file, folder, or registry key that already exists on the target system, without deleting any existing permissions for that object
• Indicating whether you want permissions to be applied to all of a folder's subfolders and files
• Configuring permissions for a new user that is being created during the installation

InstallShield 2010 takes a three-pronged approach to fully supporting modern multi-language installations:

Windows Installer databases can now be built in a Unicode format, InstallShield projects are now stored in a Unicode format, and the InstallShield interface now supports entering and viewing Unicode characters from multiple character sets at the same time.

InstallShield 2010 now supports 64-bit COM extraction. If you are using InstallShield on a 64-bit system, it can extract COM data from a 64-bit COM server.

In order to install the data to the correct locations, the component must be marked as 64 bit.

New InstallShield prerequisites include:

• Windows Installer 4.5 (with Microsoft fix), 3.1, 3.0, and 2.0
• .NET Framework 3.0 SP1 and 2.0 SP2
• Internet Explorer 8
• Microsoft SQL Server 2008 SP1 and 2005 Express SP3
• Microsoft Visual C++ 2005 SP1
• Oracle 11g Instant Client 11.1.0.7
• Crystal Reports Basic for Visual Studio 2008

MSI, InstallScript, and InstallScript MSI projects created with InstallShield 2010 can display billboards to your end users during the installation process.

Billboards are an ideal way to educate end users in new features and advertise other related products. Each billboard is a file that you or your company's graphics department creates for complete control over the look and feel of the file transfer. InstallShield 2010 supports the use of Adobe Flash application file (.swf), .bmp, .gif, .jpg, and more as billboards.

InstallShield 2010 includes support for HTML controls on dialogs in InstallScript and InstallScript MSI projects. HTML controls enable you to use HTML markup for dialog controls.

You can include on dialogs links to Web pages, installed HTML files, and HTML support files. If an end user clicks the hyperlink on the runtime dialog, you can have the HTML page open in an Internet browser, or you can trigger other behavior that you have defined through your InstallScript code.

The HTML control lets you use any valid HTML markup, including styles to control their appearance.

InstallShield is once again revolutionizing software installations with new support for application virtualization with Microsoft® App-V™.

Now when you build a traditional MSI project, InstallShield 2010 can simultaneously build it as a virtual App-V package. It can also automatically modify your legacy MSIs to App-V packages. InstallShield 2010 handles all the conversion work, so there’s no learning curve for developers new to application virtualization.

To an end user, virtual applications appear and function just like physically installed software. But virtual applications never get installed on the client. Instead they run in their own isolated virtual containers – which include registry entries, libraries, executables, and anything else the application needs to run – completely separate from the operating system. Because there’s no physical installation, there are no installation or retirement problems and no application compatibility issues.

InstallShield 2010’s App-V support is ideal for companies adopting application virtualization for their own environments. Virtual formats like App-V are also useful for software vendors offering evaluation versions of their products. Many end users are hesitant to install evaluations because of the potential risk to their machines. With InstallShield 2010, developers can offer evals as virtual packages, eliminating those fears and increasing evaluations.

Microsoft’s release of Windows 7 will be a major event in 2009. Companies reluctant to adopt Windows Vista are expected to make the move to Windows 7, and software vendors will need to make sure their products are compatible with the new OS.

InstallShield 2010 has the tools developers need to get a head start on supporting Windows 7. It makes it easy to create applications that meet Microsoft’s requirements for the “Compatible with Windows 7” logo.

InstallShield 2010 makes it easy to install applications on Windows Server 2008 R2. You can now specify that your installation requires Windows Server 2008 R2 and build conditions for features and components.

Windows Installer 5 is available with the releases of Windows 7 and Windows Server 2008 R2. With InstallShield 2010’s own implementation of Windows Installer 5 features, you can take advantage of the cool new MSI 5 functionality, including:

• Creating per-user applications
• Quicker installations for large packages

InstallShield is the ultimate setup solution for .NET software developers with full support for Visual Studio, including Visual Studio 2008 and 2005.

InstallShield lets you create your installations within the same Visual Studio interface where you create your products, making .NET install authoring more efficient. All InstallShield's views are presented within the Visual Studio .NET Solution Explorer in a separate window, so no scrolling is necessary and side-by-side viewing options are available.

With full .NET integration and support, InstallShield gives you everything you need to efficiently author reliable .NET software installations. You have the option of creating installations directly within the Visual Studio interface or using the intuitive InstallShield IDE. You can also link the primary outputs of your .NET projects to your installs, scan C# and .NET projects for file dependencies, configure .NET custom actions, distribute the .NET Framework or .NET Compact Framework, and much more.

InstallShield ensures your .NET installations are always current and reliable. It dynamically links your install project to other Visual Studio .NET project outputs, automatically updating your installation with your latest source files every time your product is built. Your installation projects also automatically include both Debug and Release build configurations, ensuring the proper source files will be included in your build.

Support customers around the world by enabling one installation to support 35 runtime languages for Windows installations, including support for Arabic and Hebrew.

Multilingual support lets you localize your installations, eliminating hundreds of hours of installation dialog and message box translation effort. Additional languages can be added easily. Changes and additions to existing translations are made with a three-step process: export all or part of the associated string tables, make the changes, and re-import them.

The power of multilingual support can also be combined with installation conditions in InstallShield to create installations that include different files, registry entries, and other resources for each of your supported languages. The conditions will assure that only the correct resources get installed for each language.

Supported languages

Arabic	Indonesian	Russian
Chinese (Simplified)	Japanese	Thai
Chinese (Traditional)	Korean	Turkish
English	French (Canada)	Portuguese (Brazil)
Basque	French (France)	Portuguese (Portugal)
Bulgarian	German	Romanian
Catalan	Greek	Serbian
Croatian	Hebrew	Slovak
Czech	Hungarian	Slovenian
Danish	Italian	Spanish
Dutch	Norwegian	Swedish
Finnish	Polish

InstallShield provides a Standalone Build module that enables you to maintain a clean build system by using the part of InstallShield that compiles the installations, plus any redistributables that you want to include in your installations. This clean build system gives you more control over the quality of the installations that you compile.

The Standalone Build module can coexist with other versions of InstallShield, and you can run it from the command line. Each full license of InstallShield Premier Edition includes 10 Standalone Build modules.

 

In addition to the validation tests added to the Windows Vista Logo certification testing suite, InstallShield comes with the InstallShield Best Practices (ISBP) validation suite. Validators in this suite alert you if your installation violates any best-practices guidelines.

• ISBP01: Verifies that no feature is named 'ALL'.
• ISBP02: Verifies that no directory is named 'DATABASE'.
• ISBP03: Verifies that no ComboBox is shorter than 50 units.
• ISBP04: Verifies that properties used on dialogs are secure or restricted public properties.
• ISBP05: Verifies that no ControlEvent condition is NULL.
• ISBP06: Verifies that InstallUISequence custom actions are also sequenced in the InstallExecuteSequence.
• ISBP07: Verifies that all features have associated components and all components are associated with features.
• ISBP08: Verifies that ARPINSTALLLOCATION is set after CostFinalize in the InstallExecuteSequence.
• ISBP09: Verifies that LIMITUI is not set without ARPNOMODIFY.
• ISBP10: Verifies that AppSearch properties are secure or restricted public properties.
• ISBP11: Verifies that no precompiled .NET assemblies are being distributed.
• ISBP12: Verifies that no file is self-registered.
• ISBP13: Verifies that properties set by dialog controls and used in the installation have a default value.
• ISBP14: Verifies that each file has the correct version information or an MsiFileHash entry.
• ISBP15: Verifies that no RadioButtonGroup has Text defined.
• ISBP16: Verifies that each component with a 64-bit destination is marked as a 64-bit component.

Not only does improved validation testing increase the usefulness of InstallShield as a tool to prepare your applications for Windows 7 and Vista Logo certification, with ISBP, you can now avoid common installation issues.

Enable a prospective customer to use the latest version of your product-with all of its features fully available-on a trial basis. No dongle is used to limit or lock software access. After a predetermined trial period, the trialware securely expires, and it no longer runs on the prospect's machine.

With the Trialware view, you can configure a product version key for your product to protect it from piracy. Using InstallShield to protect your product lets you:

• Invest minimal time and expense to turn your product into trialware.
• Set firm expiration dates using sophisticated, flexible security technology that blocks unauthorized extensions of trialware.
• Specify hyperlinks that should be displayed in the trialware run-time dialogs, which are launched whenever end users launch a protected application. The hyperlinks direct users to Web pages that inform them, for example, how to purchase your product.

With the Trialware view, you can configure a product version key for trialware. InstallShield uses the product version key to wrap a secure shell around your product's executable file (.exe). The .exe file can be unwrapped and used only according to the product version key settings that you configure, such as the number of days in the trial period.

Automation interface improvements in InstallShield give you more automation flexibility, lowering the number of times manual intervention through the IDE is required. Enhancements include automating functionality that was previously only available via the IDE.

The OverrideSystemAttributes, OverrideSystemSize, OverrideSystemVersion, and OverrideSystemLanguage properties are now available for the ISWiFile object in the automation interface; they replace the UseSystemSettings property, which is obsolete. In addition, the DeleteSubFolder and DeleteShortcut methods are now available for the ISWiFolder object. Other improvements include:

• OverrideSystemAttributes—To override the development system's settings for all of the file attributes, such as Hidden, ReadOnly, Vital, and System, set this property to True. If you set this property to False, the Hidden, ReadOnly, Vital, and System properties are ignored. 
• OverrideSystemSize—To override the development system's file size, set this property to True. If you set this property to False, the Size property is ignored. 
• OverrideSystemVersion—To override the development system's file version, set this property to True. If you set this property to False, the Version property is ignored. 
• OverrideSystemLanguage—To override the development system's file language, set this property to True. If you set this property to False, the Languages property is ignored. DeleteSubFolder—Deletes the specified subfolder from the current folder.
• DeleteShortcut—Deletes the specified shortcut from the current folder.

InstallShield is the most advanced solution ever built for creating script-based installations. InstallShield is the ultimate tool for leveraging the powerful and easy-to-use InstallScript language. With over 445 predefined installation-related functions, InstallScript enables script-based customization of any part of the installation, including the user dialog sequence, file transfer, error handling, reboot, and even uninstallation. InstallShield's scripting functionality ensures you meet your every installation requirement.
 
InstallShield offers you maximum power and flexibility by enabling any level of install customization. Source code control integration makes InstallScript project versioning possible, while the automation interface dramatically increases the number of ways in which projects can be updated programmatically. InstallShield's simplified patch and upgrade creation, clean build system support, and build report tools also assist in your product lifecycle management.
 
Complementing InstallShield's vast functionality and tool selection is its remarkable ease of use. You can use the Project Assistant to walk you through any script-based installation-authoring process, saving you significant development time. InstallShield can also add the latest source files at build time via linked folders, automatically find required file dependencies, and intelligently add third-party technology dependencies using over 70 technology modules. InstallShield does it all!

Plus, InstallShield enables you to add InstallShield prerequisites to your InstallScript projects. InstallShield prerequisites are redistributables that usually install a product or technology framework required by your application.

Use the Visual Dialog Editor to easily modify existing installation dialogs (dozens are included) or create completely new dialogs, tailoring the user interface experience for your customers.

A Dialog Creation Wizard allows you to select a dialog template and insert the dialog at any location in the user interface sequence. The new dialog will be automatically linked to the previous and following dialogs.

Dialogs can be exported and imported for sharing across projects, making project collaboration more efficient.

InstallShield makes it easy for software developers to create reliable, high-quality software patches and upgrades that can modify all aspects of a previously deployed package.
 
Everything you need to efficiently build Windows Installer (MSI) or InstallScript™ patches and updates. With InstallShield, you can easily author patches and updates that seamlessly modify any aspect of your previously installed applications. From a simple hot fix to a major upgrade, software updates built with InstallShield guarantee your customers always have the latest versions of your products. And InstallShield has rigorous automated quality-control tools that ensure installing your patches and updates never damages your customers' systems - or trust in you.
 
InstallScript patch and update creation made easy. Just use InstallShield's Release Wizard to create differential media that contains only the changed files from the original InstallScript installation to your new, updated one. Then distribute the differential media as part of an update install that includes an "update-aware" script. The script gives you the option to customize your customer's update experience with update-specific dialogs.
 
Advanced MSI patch and upgrade capabilities. InstallShield's MSI QuickPatch™ tool lets you quickly create reliable patches by simply pointing to your existing MSI installation and identifying whatever changes you wish to make - InstallShield captures the changes for you automatically. Managing QuickPatch technology is a breeze with the history view. It allows you to quickly analyze previous QuickPatches made to a particular project. InstallShield also has full patch design and upgrade views for you to author even the most complex, customized software updates. Validation for all patches and updates occurs automatically to ensure they always function properly and follow Microsoft guidelines.
 
Get patches and updates to your customers more easily. Whether you wish to distribute your InstallScript and MSI upgrades via the Internet,
CD-ROM, FLEXnet Connect, or any other method, InstallShield makes it happen.

Enhancements to the Setup Prerequisite Editor in InstallShield let you flexibly and easily redistribute setup prerequisites:

• Improved user interface give you menus that list easy-to-access commands.
• The Behavior tab lets you specify whether end users may skip the prerequisite installation. You can also specify how the prerequisite installation should proceed if it appears that the target machine does or does not need to be restarted. 
• Create prerequisite installation conditions for DWORD registry comparisons. You can also create conditions for 64-bit machines.
• Specify different methods for supplying each individual setup prerequisite in your installation. This enables you to store some of the setup prerequisite files on the source media; compress some of the setup prerequisite files into Setup.exe, to be extracted at run time; and download some of the setup prerequisite files.
• Assign release flags to setup prerequisites; include and exclude any combinations of setup prerequisites when you build different releases. 

You can use the intuitive Project Assistant to seamlessly guide you through the installation-authoring process. The Project Assistant offers a simplified look at the project data, and allows you to switch to more detailed views and back again while maintaining all updates.

The Project Assistant reduces the time required for new users or setup authors unfamiliar with either Windows Installer or smart device install formats to complete an installation project quickly. It also enables veteran setup authors to save time by more efficiently jumpstarting a new installation project.

InstallShield has unparalleled Windows Installer support, giving you complete control over your MSI installations.

Use InstallShield's powerful wizards, task-based views, and a full Direct Table Editor to easily enable your installs to leverage Windows Installer service benefits (such as install-on-demand, auto-repair, and installation rollback). With InstallShield you can easily create or edit an MSI file directly using rich views and create or edit a transform based on an existing MSI file. Plus InstallShield gives you enhanced control and error management capabilities with a MSI debugger, MSI differencing tools, and instant access to InstallShield Error Central.

InstallShield offers you maximum power and flexibility by enabling any level of install customization. Source code control integration makes MSI project versioning possible, while the automation interface dramatically increases the number of ways in which projects can be updated programmatically. InstallShield's simplified patch and upgrade creation, clean build system support, debugging, and build report tools also assist in your product lifecycle management.

What is MSI?

The Microsoft Windows Installer (MSI) service is a native service of Windows 7, Windows Vista, Windows XP, Windows 2000, Windows Me, Windows Server 2008, and more. It is also available as an add-on service for Windows NT 4, Windows 98, and Windows 95. The Windows Installer service enables the operating system to track installed applications and manage components that are shared by various applications.

• Automatically repair key product files that have been corrupted
• Advertise applications without initially loading software on a system
• Install/uninstall applications with component-level management
• Roll back to a computer's original state during an interrupted installation

Windows Installer can be described as a combination of two major components:

1. A set of guidelines and APIs for software developers, and
2. The services designed to process commands put forth by the APIs; these services include a Client Install

It is also an Install Service that can run with elevated administration privileges.

Internet Information Services (IIS) is a Web server developed by Microsoft. It provides a secure platform for building and deploying Web-based applications, managing Web sites, and publishing information to the Internet or an intranet.

InstallShield 2010 has significantly improved IIS-related functionality that makes it even easier to create and manage new IIS Web sites, Web applications, virtual directories, application pools, and Web service extensions.

InstallShield 2010 has enhanced its Internet Information Services view to look similar to IIS 7. The settings are now displayed in grids, instead of on tabs. And the grids have buttons that let you sort the grid settings by category or alphabetically. Longtime users of InstallShield will notice and appreciate the difference right away. (Available in InstallShield Premier and Professional Editions only).

InstallShield 2010 now gives developers the ability to add IIS Web applications to IIS Web sites and configure as needed. Plus, you can now create an IIS virtual directory without an application. Both enhancements were popular requests by the InstallShield community.

InstallShield 2010 has a new IIS Scanner that analyzes and records IIS data about a Web site’s settings – including its virtual directories, applications, and application pools – and imports it into the Internet Information Services view. So instead of having to waste time manually entering data, InstallShield 2010 finds it and adds it for you. Developers can then use that view to make any changes to the IIS settings. (Available in InstallShield Premier Edition only).

In addition, InstallShield 2010 Premier and Professional Editions have new IIS settings that our users have specifically requested, including:

• Managed Pipeline Mode: Specify the appropriate request-processing pipeline mode—either integrated or classic—for an application pool.
• Enable 32-Bit Applications: Specify whether you want to allow 32-bit applications in the selected application pool to be run on 64-bit systems.
• .NET Framework Version: Specify the version of the .NET Framework that an application pool should load.
• ASP.NET Platform: For installations that may run on a 64-bit version of Windows with the .NET Framework, specify which ASP.NET platform should be used to map a Web site, application, or virtual directory to the ASP.NET version.

InstallShield is once again revolutionizing software installations with new support for application virtualization with Microsoft® App-V™.

Now when you build a traditional MSI project, InstallShield 2010 can simultaneously build it as a virtual App-V package. It can also automatically modify your legacy MSIs to App-V packages. InstallShield 2010 handles all the conversion work, so there’s no learning curve for developers new to application virtualization.

To an end user, virtual applications appear and function just like physically installed software. But virtual applications never get installed on the client. Instead they run in their own isolated virtual containers – which include registry entries, libraries, executables, and anything else the application needs to run – completely separate from the operating system. Because there’s no physical installation, there are no installation or retirement problems and no application compatibility issues.

InstallShield 2010’s App-V support is ideal for companies adopting application virtualization for their own environments. Virtual formats like App-V are also useful for software vendors offering evaluation versions of their products. Many end users are hesitant to install evaluations because of the potential risk to their machines. With InstallShield 2010, developers can offer evals as virtual packages, eliminating those fears and increasing evaluations.

In addition to the validation tests added to the Windows Vista Logo certification testing suite, InstallShield comes with the InstallShield Best Practices (ISBP) validation suite. Validators in this suite alert you if your installation violates any best-practices guidelines.

• ISBP01: Verifies that no feature is named 'ALL'.
• ISBP02: Verifies that no directory is named 'DATABASE'.
• ISBP03: Verifies that no ComboBox is shorter than 50 units.
• ISBP04: Verifies that properties used on dialogs are secure or restricted public properties.
• ISBP05: Verifies that no ControlEvent condition is NULL.
• ISBP06: Verifies that InstallUISequence custom actions are also sequenced in the InstallExecuteSequence.
• ISBP07: Verifies that all features have associated components and all components are associated with features.
• ISBP08: Verifies that ARPINSTALLLOCATION is set after CostFinalize in the InstallExecuteSequence.
• ISBP09: Verifies that LIMITUI is not set without ARPNOMODIFY.
• ISBP10: Verifies that AppSearch properties are secure or restricted public properties.
• ISBP11: Verifies that no precompiled .NET assemblies are being distributed.
• ISBP12: Verifies that no file is self-registered.
• ISBP13: Verifies that properties set by dialog controls and used in the installation have a default value.
• ISBP14: Verifies that each file has the correct version information or an MsiFileHash entry.
• ISBP15: Verifies that no RadioButtonGroup has Text defined.
• ISBP16: Verifies that each component with a 64-bit destination is marked as a 64-bit component.

Not only does improved validation testing increase the usefulness of InstallShield as a tool to prepare your applications for Windows 7 and Vista Logo certification, with ISBP, you can now avoid common installation issues.

Support customers around the world by enabling one installation to support 35 runtime languages for Windows installations, including support for Arabic and Hebrew.

Multilingual support lets you localize your installations, eliminating hundreds of hours of installation dialog and message box translation effort. Additional languages can be added easily. Changes and additions to existing translations are made with a three-step process: export all or part of the associated string tables, make the changes, and re-import them.

The power of multilingual support can also be combined with installation conditions in InstallShield to create installations that include different files, registry entries, and other resources for each of your supported languages. The conditions will assure that only the correct resources get installed for each language.

Supported languages

Arabic	Indonesian	Russian
Chinese (Simplified)	Japanese	Thai
Chinese (Traditional)	Korean	Turkish
English	French (Canada)	Portuguese (Brazil)
Basque	French (France)	Portuguese (Portugal)
Bulgarian	German	Romanian
Catalan	Greek	Serbian
Croatian	Hebrew	Slovak
Czech	Hungarian	Slovenian
Danish	Italian	Spanish
Dutch	Norwegian	Swedish
Finnish	Polish

InstallShield 2010 takes a three-pronged approach to fully supporting modern multi-language installations:

Windows Installer databases can now be built in a Unicode format, InstallShield projects are now stored in a Unicode format, and the InstallShield interface now supports entering and viewing Unicode characters from multiple character sets at the same time.

InstallShield provides a Standalone Build module that enables you to maintain a clean build system by using the part of InstallShield that compiles the installations, plus any redistributables that you want to include in your installations. This clean build system gives you more control over the quality of the installations that you compile.

The Standalone Build module can coexist with other versions of InstallShield, and you can run it from the command line. Each full license of InstallShield Premier Edition includes 10 Standalone Build modules.

 

A repository is a collection of common elements can be shared and reused in different installation projects for quickly rolling out new setups. Examples of elements that can be stored in a repository include end-user dialogs, InstallScript™ files, merge modules, SQL scripts, system searches, and project templates. Repositories provide you with the ability to reuse project elements in multiple projects to ensure consistency. They also save you from having to duplicate work. For example, if many of the installations for your organization's products include a particular custom dialog, you can create that custom dialog once and then publish it to your repository. Any time you want to use that dialog in another installation, simply add the dialog from your repository to your project. Two types of repositories are available: 

• Local repository - A local repository is your own collection of installation elements that you want to be able to reuse in multiple projects. A local repository is stored on your local machine, and it is not available to other installation authors.
• Network repository - A network repository is a collection of installation elements that multiple installation authors can access and reuse in their projects as needed. A network repository fosters collaboration among installation authors; it is stored on a network.

Virtual machines have been a licensing and compliance challenge for software vendors. If you don’t want your products to run on virtual machines, InstallShield 2010 has the answer.

It can now build installations that detect when they are being run on virtual machines like Microsoft Hyper-V and Virtual PC or VMware and optionally block the installation.

For applications that run in locked-down environments, InstallShield 2010 has new functionality that significantly improved the way installations set files, folders, and registry keys at run time.

Developers frustrated with the traditional Windows Installer LockPermissions option will appreciate the improvements, none of which are supported by the old option, including:

• Support for many well-known security identifiers (SIDs) such as guest, everyone, and administrator
• Support for localized user names, which could cause the installation to fail in the traditional option
• Denying a user or group from having the permissions you are specifying
• Adding permissions to a file, folder, or registry key that already exists on the target system, without deleting any existing permissions for that object
• Indicating whether you want permissions to be applied to all of a folder's subfolders and files
• Configuring permissions for a new user that is being created during the installation

InstallShield lets you give your MSIs the ability to install multiple instances of the same product on the same machine. It gives you even more flexibility when creating installations.

At build time, InstallShield creates a product code–changing instance transform for each instance and streams the instance transforms into the .msi package. At run time, the setup launcher displays a new instance selection dialog that lets end users specify whether they want to install a new instance, or update or maintain an already installed instance.

InstallShield lets you add Windows Installer packages to Basic MSI and InstallScript MSI projects as chained MSI packages.

If your Basic MSI or InstallScript MSI installation includes chained MSI packages and Windows Installer 4.5 or later is present on the target system, the Windows Installer installs the multiple packages as a single transaction.

If one or more of the packages in the transaction cannot be installed successfully or if the end user cancels the installation, the Windows Installer initiates rollback for all packages to restore the system to its earlier state.

InstallShield lets you associate InstallShield prerequisites with features to chain multiple MSIs together in a single installation.

It ensures that when your end users install a feature, the prerequisite is also installed (if it wasn’t already on their machine). Feature prerequisites are useful for applications or components that are used by only some configurations of the installed product and are not used during the installation itself.

InstallShield also still supports setup prerequisites not associated with any features. Setup prerequisites are installed before the main installation begins. They are useful for base applications and technology frameworks that must be installed for all configurations of the installed product or that provide functionality that is used during the installation itself.

Automation interface improvements in InstallShield give you more automation flexibility, lowering the number of times manual intervention through the IDE is required. Enhancements include automating functionality that was previously only available via the IDE.

The OverrideSystemAttributes, OverrideSystemSize, OverrideSystemVersion, and OverrideSystemLanguage properties are now available for the ISWiFile object in the automation interface; they replace the UseSystemSettings property, which is obsolete. In addition, the DeleteSubFolder and DeleteShortcut methods are now available for the ISWiFolder object. Other improvements include:

• OverrideSystemAttributes—To override the development system's settings for all of the file attributes, such as Hidden, ReadOnly, Vital, and System, set this property to True. If you set this property to False, the Hidden, ReadOnly, Vital, and System properties are ignored. 
• OverrideSystemSize—To override the development system's file size, set this property to True. If you set this property to False, the Size property is ignored. 
• OverrideSystemVersion—To override the development system's file version, set this property to True. If you set this property to False, the Version property is ignored. 
• OverrideSystemLanguage—To override the development system's file language, set this property to True. If you set this property to False, the Languages property is ignored. DeleteSubFolder—Deletes the specified subfolder from the current folder.
• DeleteShortcut—Deletes the specified shortcut from the current folder.

Enhancements to the Setup Prerequisite Editor in InstallShield let you flexibly and easily redistribute setup prerequisites:

• Improved user interface give you menus that list easy-to-access commands.
• The Behavior tab lets you specify whether end users may skip the prerequisite installation. You can also specify how the prerequisite installation should proceed if it appears that the target machine does or does not need to be restarted. 
• Create prerequisite installation conditions for DWORD registry comparisons. You can also create conditions for 64-bit machines.
• Specify different methods for supplying each individual setup prerequisite in your installation. This enables you to store some of the setup prerequisite files on the source media; compress some of the setup prerequisite files into Setup.exe, to be extracted at run time; and download some of the setup prerequisite files.
• Assign release flags to setup prerequisites; include and exclude any combinations of setup prerequisites when you build different releases. 

With unit testing in InstallShield, you can test just the XML file changes without having to build and run your entire installation.

The XML File Changes view supports namespaces in XML files. With quick and easy XML testing, you can increase the reliability of XML configurations.

InstallShield brings you deeper XML support—letting you create more flexible installations by specifying the XML encoding of an XML file.

With InstallShield,  you can require that end users scroll through the complete End-User License Agreement (EULA) before installation can proceed.

InstallShield includes support for disabling the Next button on the LicenseAgreement dialog until the end user reaches the end of the EULA text in the scrollable EULA control through mouse or keyboard scrolling. The end user must also select the "I accept the terms in the license agreement" option before the Next button is enabled; this behavior is the same as with earlier releases of InstallShield.

The scroll requirement is not available in the LicenseAgreement dialog by default. To use this functionality, you must add to your project the Windows Installer DLL custom action called WatchScroll. This custom action calls the EulaScrollWatcher.dll file. In addition, you must modify the Next button's Control conditions and add an event to the Memo control. This is available for Basic MSI projects.

InstallShield enables you to add a merge module that contains .dim files to any project type that supports merge modules—for example, Basic MSI, InstallScript, and Direct MSI projects. You can also add a merge module that contains .dim files to another merge module as a dependency.

Merge Module projects now include the DIM References view, which was previously available only in Basic MSI projects. The DIM References view lets you add to your project .dim files that were created with InstallShield Collaboration or InstallAnywhere Collaboration.

Starting with Windows XP, instead of writing COM information to the registry on a target system, you can write COM information to an application manifest file, which is an XML file that contains information about an application and the libraries it depends on. Use the Reg-Free COM Wizard in InstallShield to create and modify registry-free manifest files to include in your installations.

A local repository is your own collection of installation elements that you want to be able to reuse in multiple projects. A local repository is stored on your local machine, and it is not available to other installation authors. Examples of elements that can be stored in a repository include end-user dialogs, InstallScript™ files, merge modules, SQL scripts, system searches, and project templates.
 
Repositories provide you with the ability to reuse project elements in multiple projects to ensure consistency. They also save you from having to duplicate work. For example, if many of the installations for your organization's products include a particular custom dialog, you can create that custom dialog once and then publish it to your repository. Any time you want to use that dialog in another installation, simply add the dialog from your repository to your project.

 

InstallShield provides functionality to select an existing Windows user account or create a new one at installation time.

• Select an existing Windows user account at installation time. Many server applications require the specification of a named user account to enable a server application to access resources restricted to other users. This restricted resource access is a fundamental construct in creating secure applications.
• Create a new Windows user account at installation time. System Administrators may decide to create a user account explicitly for an application. This limits the resource access for a given user account to only those resources required to run the application.

InstallShield is the most advanced solution ever built for creating script-based installations. InstallShield is the ultimate tool for leveraging the powerful and easy-to-use InstallScript language. With over 445 predefined installation-related functions, InstallScript enables script-based customization of any part of the installation, including the user dialog sequence, file transfer, error handling, reboot, and even uninstallation. InstallShield's scripting functionality ensures you meet your every installation requirement.
 
InstallShield offers you maximum power and flexibility by enabling any level of install customization. Source code control integration makes InstallScript project versioning possible, while the automation interface dramatically increases the number of ways in which projects can be updated programmatically. InstallShield's simplified patch and upgrade creation, clean build system support, and build report tools also assist in your product lifecycle management.
 
Complementing InstallShield's vast functionality and tool selection is its remarkable ease of use. You can use the Project Assistant to walk you through any script-based installation-authoring process, saving you significant development time. InstallShield can also add the latest source files at build time via linked folders, automatically find required file dependencies, and intelligently add third-party technology dependencies using over 70 technology modules. InstallShield does it all!

Plus, InstallShield enables you to add InstallShield prerequisites to your InstallScript projects. InstallShield prerequisites are redistributables that usually install a product or technology framework required by your application.

Edit MSI packages without having to convert them to an ISM project and save the changes made into a transform (MST) file.

Opening Existing Transforms for Editing
Browse for an existing MST file. Before InstallShield can open the MST file, it needs the base MSI to which this file should be applied. Also, it requires the names of any additional MSTs that should be applied to the base MSI before opening the MST for editing.

The first time you open an MST file, the MST Wizard launches. This wizard allows you to specify the MST file (completed by default), the base MSI file, and any additional transforms to apply before editing. When the wizard is finished, the transforms are applied and the MST opens in the IDE in Direct MST mode. The data specified in the wizard is saved so the next time the file is opened, the MST opens directly in the IDE.

Creating New Transform Projects
You can use the transform project type to create a new MST for editing. As with opening an existing transform, when you create a new transform project, the MST Wizard launches.

The MSI debugging tools ensure your installations always function as expected. InstallShield lets you step through both the Windows Installer user interface sequence and execute sequence to confirm conditional behavior or to identify and eliminate trouble spots in your install. Break points can be set and variables can be monitored. When custom actions are encountered, the appropriate debugging tool can be launched.

You can also validate your packages for internal consistency and compliance with Microsoft guidelines, and test run an install without transferring files. In addition, build reports can be generated to review installation project contents.

The source code control (SCC) integration gives you the power to manage and edit your installation projects the same way you manage your other code. Installations authored using  InstallShield can be easily checked in and out of source code control no matter which SCC solution you use, ensuring greater consistency between your applications and installations. InstallShield is capable of interacting with any source code control system that complies with the Microsoft SCC Interface, including Microsoft Visual SourceSafe®, Rational ClearCase®, Merant PVCS®, and more. Save projects in XML format, making them far easier to manage and manipulate. XML project files integrate more efficiently with source code control than a binary file and enable additional command-line processes to be built around installation authoring.

XML project files integrate more efficiently with source code control tools than a binary file and enable additional command-line processes to be built around installation authoring.

InstallShield makes it easy for software developers to create reliable, high-quality software patches and upgrades that can modify all aspects of a previously deployed package.
 
Everything you need to efficiently build Windows Installer (MSI) or InstallScript™ patches and updates. With InstallShield, you can easily author patches and updates that seamlessly modify any aspect of your previously installed applications. From a simple hot fix to a major upgrade, software updates built with InstallShield guarantee your customers always have the latest versions of your products. And InstallShield has rigorous automated quality-control tools that ensure installing your patches and updates never damages your customers' systems - or trust in you.
 
InstallScript patch and update creation made easy. Just use InstallShield's Release Wizard to create differential media that contains only the changed files from the original InstallScript installation to your new, updated one. Then distribute the differential media as part of an update install that includes an "update-aware" script. The script gives you the option to customize your customer's update experience with update-specific dialogs.
 
Advanced MSI patch and upgrade capabilities. InstallShield's MSI QuickPatch™ tool lets you quickly create reliable patches by simply pointing to your existing MSI installation and identifying whatever changes you wish to make - InstallShield captures the changes for you automatically. Managing QuickPatch technology is a breeze with the history view. It allows you to quickly analyze previous QuickPatches made to a particular project. InstallShield also has full patch design and upgrade views for you to author even the most complex, customized software updates. Validation for all patches and updates occurs automatically to ensure they always function properly and follow Microsoft guidelines.
 
Get patches and updates to your customers more easily. Whether you wish to distribute your InstallScript and MSI upgrades via the Internet,
CD-ROM, FLEXnet Connect, or any other method, InstallShield makes it happen.

Sometimes one installation doesn't fit with every end user. Whether you're a developer creating installations for use by various departments on a corporate network or if you just have a wide range of end users, you probably need to develop your installation to meet multiple sets of requirements.

The Release Wizard is your key to quickly building your distribution media. You can create different CDs with different components if that's your preferred distribution method. Or you can build a single project that contains as many different flavors of your installation as is necessary for your varied end users.

You can generate project outlines that can be used over and over again, enhancing project efficiency.
 
A project template (.ist file) contains all of the default settings and design elements that you want to use as a starting point when you create an installation project or merge module project.
 
You can open a template in InstallShield and edit it as you would a project. To create a template, save any project as an .ist file.
 
InstallShield project templates serve only as a starting point for new projects. After you have created a project based on a template, there is no link between the current project and the existing template. If you change an element in the template, it does not affect the project that you created based on that template. However, you can modify the template and create another project based on the updated version of the template.

This helps to ensure your products are installed properly in a variety of scenarios.

This view and its subviews do not appear in the following project types:

• InstallScript
• InstallScript Object
• QuickPatch
• Smart Device

InstallShield provides the Windows Installer capability in the System Search view to locate a particular file, folder, registry key, .ini file value, or .xml file value on a target system prior to installation. Essentially, this feature lets you perform application, version, and configuration data searches.

The System Search view displays a grid listing each search that you want to conduct on the target system. You can use this view to add a predefined system search—whether it is a search that is included with InstallShield or one that is stored in a repository—to your project. You can also use the System Search view to customize any predefined searches or define your own system searches for your installation.

Whenever you define your own search, the System Search Wizard is launched. From there, you can select from a list of search options and specify search details, such as the number of subfolder levels to search. When you modify an existing search, you can alter your initial selections in the System Search Wizard.

Media spanning functionality enables you to build an installation that spans more than one CD, DVD, or other media, so you never have to impose limits on the size of your application.
 
For example, if the installation's payload is too large to fit onto one CD or DVD, the installation is automatically built onto multiple pieces of that media.

The user-friendly automation interface makes it easy to edit virtually any element of an installation project programmatically.
 
Automate the build process by building your project from the command line with powerful command-line tools. Change product name and upgrade code, release settings, summary information stream items, release flags, and any property—in addition to initiating the build process and adding/changing/removing features, components, registry entries, files, and more.
 
These capabilities will enhance routine build processes, such as those that run during non-business hours. They will be especially useful in cases where many projects or many versions of the same project need to be modified prior to build.

While past InstallShield versions only supported partial file-set signing (e.g., .msi, .hdr, and Setup.exe files) InstallShield comes with enhanced support for digital signatures, letting you save time by digitally signing all your files at build time.  This includes signing with certificates stored in .pfx files (in addition to InstallShield's pre-existing ability to sign with certificates stored in .spc+.pvk file pairs).

To change the icon that is used for a shortcut, you can right-click on the shortcut and then click the Change Shortcut icon command. InstallShield opens the Change Icon dialog box, which enables you to select the icon file and associated icon index that should be used when the shortcut is created on target systems at run time.
 
Shortcuts that are listed in the Shortcuts explorer now show the icon image that will be used on the target system. Previously, the Shortcuts explorer used a different image for all types of shortcuts, even if an icon was specified for the shortcut.

 

InstallShield gives you the ability to change the Product Version from the Command Line or through an MSBuild Task Parameter. Using the -y command-line parameter or the InstallShield task ProductVersion parameter is especially helpful if you want to increment the build version (the third field) of the product version.

The ability to override Windows Installer Property Values from the Command Line or through an MSBuild Task Parameter lets you override or create the property if it does not exist.

Each time you build an installation, a log and build report are generated. The log contains the same information displayed in the Output window during the build process. The build report contains a concise summary of your build, as well as a listing of all features and files included in your build. Since both the log and report are generated and time-stamped each time you build the installation, you can use these for manual verification of the contents of installations, as well as for your records.

To prevent InstallShield from extracting undesired COM data from a COM server, you can edit a new Filters.xml file that is installed with InstallShield. Editing this Filters.xml file enables you to customize the list of registry keys that will be excluded from COM extraction.

The Filters.xml file also now lists files that the Static, Dynamic, and Visual Basic dependency scanners will exclude or include. Previously, two different file—Userscan.ini and Iswiscan.ini—were used to list excluded and included files.

InstallShield supports the Microsoft Build engine (MSBuild) included with the .NET Framework.  MSBuild support allows you to build Visual Studio solutions with InstallShield projects in build lab environments where Visual Studio is not installed. MSBuild is an extensible build framework designed to remove the build dependence on Visual Studio.
 
InstallShield Express users: Since Express does not support the standalone build, MSBuild will be used on a machine with the Express IDE installed. This allows you to create an automated build environment that includes both your code and your installation.

The InstallShield integration with Visual Studio now uses an MSBuild-compatible XML format project file (.isproj), which enables MSBuild to seamlessly build Visual Studio solutions that include InstallShield projects. To build solutions in a standalone environment, simply install the InstallShield Standalone Build on the build machine.

 

InstallShield now references Developer Installation Manifest (DIM) files created with the InstallShield Collaboration module. InstallShield Collaboration automatically incorporates installation requirements defined by developers into the installation project. A single license of InstallShield Collaboration is included with InstallShield Premier.

Easily check for and install any prerequisite applications or system components before your installation is executed.

Choose from our preconfigured setup prerequisites, like Internet Explorer 6 and Java 2 Runtime Environment. You can even choose to deploy your setup prerequisites with your product or download them from the Web as needed. In addition, you can design your own prerequisites from the ground up using the powerful Setup Prerequisite Editor that is included in the Premier and Professional editions of InstallShield.

InstallShield 2010 now enables you to add InstallShield prerequisites to your InstallScript projects. InstallShield prerequisites are redistributables that usually install a product or technology framework required by your application.

If you work on a mix of different project types, InstallShield 2010 lets you simplify your testing matrix by enabling you to reuse this type of redistributable in all of your Basic MSI, InstallScript, and InstallScript MSI projects.

New InstallShield prerequisites include:

• Windows Installer 4.5 (with Microsoft fix), 3.1, 3.0, and 2.0
• .NET Framework 3.0 SP1 and 2.0 SP2
• Internet Explorer 8
• Microsoft SQL Server 2008 SP1 and 2005 Express SP3
• Microsoft Visual C++ 2005 SP1
• Oracle 11g Instant Client 11.1.0.7
• Crystal Reports Basic for Visual Studio 2008

Distributing your applications via the Internet a snap with One-Click Install technology. You can offer your customers a seamless, familiar download and installation experience with a single mouse click.
 
Automatically create a Web page that contains your complete installation package for users to easily download. With One-Click Install technology, unnecessary user steps, such as responding to the cumbersome "save as" dialog and finding the location of the application on their system before installing it, are eliminated. Using this process, success rates for installations increase significantly, which means fewer support calls for you and increased customer trust in your products.
 
You can customize your One-Click Install installation to only install files not already present on the user's PC—including the Windows Installer or InstallScript™ engines—saving your customers valuable bandwidth. A default location, hosted by InstallShield, can be used for retrieval of the engines, or you can set and maintain your own. Optionally, you can also allow users to choose to save your installation to run later.
 
Special build options include digitally signing and password-protecting your installations. Additionally, LZX compression capability can be optionally used to create the smallest installation possible. This is ideal for a final build before Web distribution.

Access this dialog from the Script Text field in the properties grid of VB/JScript custom actions. In the dialog, enter the script code your custom action should execute.

Seamlessly add the setup information from a COM+ application to an installation package with absolutely no script writing using the Component Services view.

The Component Services view enables you to manage COM+ applications and components for your installation package. You can manage both COM+ server applications and application proxies. A COM+ application proxy consists of a subset of the attributes of the server application, and it enables remote access from a client machine to the machine where the application resides.

File dependency scanners are time-savers for your setup. They automatically determine the required files for your projects. For example, the Visual Basic 6 Scanner collects dependencies of a standard Visual Basic project. The Static Scanner scans portable executables (DLL, EXE, OCX, etc.) and finds out which files they need to run successfully. And the Dynamic Scanner identifies files called by an application while it is running.

You can view the results of the scanning processes in a displayed list and select which files you would like to add to your project. These lists will be pre-filtered to exclude system level files that could negatively impact the target system. A user defined filtering list is also available if changes to the filtering process are desired.

From time to time, you may need to do a little more to customize an installation to meet your individual needs. The Custom Actions view makes it easy for you to schedule a custom action, such as an EXE or VBScript file, to run at precisely the right moment in your installation.
Custom actions allow you to add functionality to your installation that is not inherently supported. These actions can be used for any task, such as displaying a Readme file or deleting a registry entry.

You can create custom action