Join us for SoftSummit 2023. The 20th anniversary of the industry leading software monetization conference. April 18 and 20. Register Now

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Level 10

HOTFIX: Visual Studio crashes when editing Visual C++ source file


When a solution contains a Visual C++ project and a InstallShield Limited Edition project, editing the code in a *.cpp file causes Visual Studio to crash


This problem is due to a bug introduced in the InstallShield 2010 Limited Edition product.

Steps to Reproduce:

1) In Visual Studio 2010, create a new solution
2) Add a new VC++ win32 Console application to the solution
3) Add a new ISLE project to the solution
4) Open any .cpp project file in the solution and click on several places in the .cpp code file.

Hot Fix:

To apply the hot fix, follow the steps below:

1. Close Visual Studio.
2. Download the hot fix .zip file attached to this thread, and uncompress the IsLimPkg.dll to a temporary location.
3. Locate the folder: \System. (By default, this directory is "C:\Program Files\InstallShield\2010LE\System")
4. Make a backup copy of file IsLimPkg.dll.
5. Copy the new IsLimPkg.dll file to \System.
6. Restart Visual Studio.

Additional Information:

This problem is being tracked internally with issue number IOA-000055687. This fix will be included in a future release of the InstallShield Limited Edition product.

Note: This hotfix also address the issue related to Visual Studio 2010 crashing after installing Power commands tool.


After Installing Power commands tool the InstallShield Limited Edition project no longer shows its context menu in the solution explorer and results in Visual Studio 2010 crashing


This problem is due to an AccessViolationException.

Steps to Reproduce:

1) Install Power Commands tool.
2) In Visual Studio 2010, create a new solution
3) Add a new Install Shield Limited Edition project to the solution
4) Click on any of the views of the InstallShield Limited Edition Project.
0 Kudos
1 Reply
Level 17

This issue is resolved in InstallShield 2011 Limited Edition. For more information, see the following community thread:
0 Kudos