Summary
How to successfully use a merge module created with Microsoft Visual Studio .NET 2003/2005/2008 that contains a .NET assembly with an Installer ClassSynopsis
This also applies to Installer Class being included with merge module created from InstallShield.
Discussion
If including a merge module that meets the following criteria, some additional steps must be taken to ensure a successful installation:
- Created with Microsoft Visual Studio .NET 2003 or 2005 or 2008
- Contains an assembly that has an Installer Class
By default, when a merge module that meets the above criteria is inserted into a project, error -1001 occurs at run time. An example of this error is as follows:
Error 1001.InstallUtilLib.dll: Unknown error in CorBindToRuntimeHost (0x80131700).
This error occurs because some additional steps must be taken to configure the project to support this type of Merge Module. Follow these steps to ensure a successful installation:
- Select the Direct Editor view.
- Select the InstallShield table in the center column.
- Create a new row in this table.
- In the Property column, enter the value: _ISSupportedRuntimes.
- In the Value column, enter a semicolon-delimited list of versions. Example: 1.1.4322;1.0.3705 or 2.0.50727 or 4.0.30319
- In Windows Explorer, create a blank file named "_isconfig.xml". See attached _isconfig.xml file for an example.
- Select the Support Files/Billboards view.
- Insert this "_isconfig.xml" file in the Language Independent section of this view.
- Select the Custom Actions view.
- Create a new custom action with the following settings:
Type: Set a property
Source: VSDFxConfigFile
Target: [SUPPORTDIR]\_isconfig.xml
- Insert this custom action as the first action in the Installation | Execute sequence via the Sequences view.
- Rebuild the project.
The file and property specified in Step 7 are created by default during the build process when the property specified in Step 4 is created in the InstallShield table. The values listed in Step 7 will not be available in the drop-down box, but must be manually entered.
Related Articles
HOTFIX: Install Fails With Error 1001 When a .NET Installer Class Component is Present in InstallShield 2015 SP1 17Number of Views Uninstall a Merge Module 3Number of Views InstallShield 11.5 Hotfix for Issues with Update 2, .NET Installer Class Support, CopyFile/XCopyFile, Activating InstallSh… 4Number of Views Insert a Custom Action into a Merge Module 3Number of Views Sequence A Custom Action In A Merge Module 7Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago