When building an installation, the following error may occur:
Warning -6245: One or more of the project's components contain .NET properties that require the .NET Framework. It is recommended that the release include the .NET Framework.
Q211088: ERRDOC: Build Warning 6245
↧
↧
Q107573: ERRDOC: Build Warning 4301
When building an InstallShield project, the following error may occur:
'Warning -4301: Could not find the .msi file <MSIFILE> for key synchronization.'
↧
Q107607: ERRDOC: Build Warning -6135
When building an InstallScript or InstallScript MSI project type, the following error may occur:
Warning -6135: The specified feature [2] is not associated with any Setup Type.
[2] is a placeholder that contains the name of the feature that is not associated with a Setup Type.
↧
Q210388: HOWTO: Display of Suite Controls Based on Feature Selection
Each suite control has both Visible and Enabled field that hides or greys out the control if the provided condition is not true.
↧
Q210546: HOTFIX: 4.5 .NET Framework Setup Prerequisite file fails to download
After installing Service Pack 1, when Microsoft .NET Framework 4.5 Full or Microsoft .NET Framework 4.5 Web Prerequisite is selected to be downloaded in from within the InstallShield 2012 Spring IDE, the following error is encountered:
The download failed; make sure you are running as Administrator, and that your machine is connected to the Internet. Would you like to try again?
In the download results pane, the following message is displayed:
The checksum of file dotnetfx45_full_x86_x64 is incorrect. Please try downloading the Merge Module or Object again
↧
↧
Q210468: HOWTO: Prevent Shortcuts from being Pinned to the Start screen
This article discusses preventing shortcuts created during installation from being pinned to the target system's Start screen.
↧
Q106362: INFO: Successfully Authoring a Patch
This article discusses rules one must follow to successfully author a patch. Failure to follow these rules can cause unpredictable and erroneous behavior during installation of the patch.
↧
Q113727: HOTFIX: Beta Support for Visual Studio 2008
This article applies to InstallShield 2008. Flexera Software no longer provides support for Installshield 2008 but as a courtesy we have left this document for any remaining Installshield 2008 users. Please read Flexera Software's end of life policy document for more information on Flexera Software's policy as well as the end of life announcement for more information. In order to continue receiving support please upgrade to our latest version. Thank you for using Installshield.
When attempting to integrate InstallShield 2008 with Visual Studio 2008, the InstallShield projects may not appear in the Visual Studio IDE.
Additionally, the following source control–related issues were resolved in this hotfix:
- 1-J2839: InstallScript context help does not work in the InstallScript view when InstallShield is used from within Visual Studio.
- IOC-000005921: Setup Design tab is not refreshed until the view is reopened in Visual Studio 2005.
- IOC-000047606: Blank solutions in Visual Studio do not work with Visual SourceSafe and InstallShield.
- IOC-000052315: Checking in and checking out solutions that include InstallShield projects does not work as expected.
- IOC-000053322: Attempting to change source control settings in Visual Studio with InstallShield results in an error message.
↧
Q107463: HOTFIX: Hotfix Available for InstallShield Developer 8.0 Users
Flexera Software no longer provides support for Developer 8.x but as a courtesy we have left this support document for any remaining Developer 8.x users. Please read Flexera Software's end of life policy as well as the end of life announcement for more information. In order to continue receiving support please upgrade to our latest version. Thank you for using InstallShield.
A hotfix has recently been released to address several key issues with InstallShield Developer 8.0. These include several issues with skins, multilingual setups, and the QuickPatch project type.
↧
↧
Q100057: HOWTO: Installing and Uninstalling Fonts In Installshield Professional 5.x
Flexera Software no longer provides support for Professional 5.x but as a courtesy we have left this document for any remaining Professional 5.x users. Please read Flexera Software's end of life policy document for more information on Flexera Software's policy as well as the end of life announcement for more information. In order to continue receiving support please upgrade to our latest version. Thank you for using InstallShield.
↧
Q201449: ERRDOC: The Imported Project Was Not Found Build Error
When building a Visual Studio solution that contains an InstallShield 2012 Project, the following build error might be encountered:
C:\Builds\3\Test Project\WFA\Sources\VS2010Projexts\WFA\Setup1\Setup1.isproj (29): The imported project "C:\Program Files (x86)\MSBuild\InstallShield\2011\InstallShield.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
↧
Q207667: ISSUE: After Upgrading an InstallShield Project, TFS Build Fails With Error, "InstallShield.targets was not found"
If a Visual Studio solution originally contains either an InstallShield 2011 or InstallShield 2012 project and the InstallShield project is upgraded to InstallShield 2012 Spring, the following error may be encountered when building using Team Foundation Server (TFS):
"TestProject.isproj (51): The imported project "C:\Program Files (x86)\MSBuild\InstallShield\2011\InstallShield.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk."
↧
Q106954: HOWTO: Monitor an MSI Install Without Creating a Log File
This article discusses how to monitor an MSI-Based installation without creating a text-based log file.
↧
↧
Q112546: HOW TO: Verbosely Log a Command Line Build
When building an InstallShield project from the IDE, command-line build or standalone build, it may be helpful to get more information if a build error occurs. This article explains how to verbosely log the build process to obtain more information.
↧
Q107923: ERRDOC: Build Error -1014
When building a project within Express, the following error occurs:
ISEXP : fatal error -1014: Cannot rename directory <PATH> to <PATH>\folder.Bak. Windows Explorer or a DOS prompt may be pointing to a subfolder of the release output folder (Disk1) or to the Interim folder, locking it. Change the current directory. Close any open files in the Disk1 folder. Close Msidb.exe if it is open.
<PATH> in the above error points to the path where setup is attempting to build the release.
↧
Q110768: ERRDOC: Component Transfer Error 0 Whe Uninstalling Pro 6.x Setup
When uninstalling a Professional 6.x installation from the setup script of a InstallShield X or later, DevStudio 9.x or Professional 7.x install and continuing on with the installation, the following component transfer error might occur during file transfer of the InstallShield 11, InstallShield 10.x, DevStudio 9.x or Professional 7.x setup:
↧
Q108842: ERRDOC: Validator Number Val0004
When performing Upgrading and Patching Validation, a validation error may occur in one of the following formats:
"Error Val0004 The component [1] contains the file [2]. This file is new to this component, but the key file for this component did not change. As a result, the new file will not get installed in an upgrade scenario. Include this file in a component whose key has changed, or place it in its own new component."
"Error Val0004 The file [2] in component [1] is different from the file in the previous package, but the key file for this component did not change. As a result, the changed file will not be installed in an upgrade scenario. Place this file in its own new component."
[1] is a placeholder that contains the component name that contains the new or changed file, while [2] contains the file name itself that is new or has been changed.
↧
↧
Q109067: ERRDOC: Build Error -6264
When building an InstallShield project, the following error may occur:
Error -6264: A record in the [1] table is using string ID [2] for column [3] but this string is blank and the column is not nullable.
[1] is a placeholder that contains the name of the table, [2] contains the specific string ID, and [3] contains the specific column generating this error.
↧
Q107174: ERRDOC: Build Error 5056
When building an InstallShield project, the following error occurs:
Error -5056: Internal build error.
↧
Q108886: ERRDOC: Build Error 5081
When building an InstallShield project, the following error may occur:
** Error: -5081: Could not write to setup.ini
↧
More Pages to Explore .....
