CODEWITHSUNDEEP
c#.netvisual-studio-2012installshield
user3712853
user3712853

Reputation:

InstallShield - Suddenly incorrect path to InstallUtilLib.dll

I have experienced the famous error 1001 today. The reason for this, was apparently that the .NET Framework File Locations for InstallShield LE were changed to the path of .NET 4.0 even though the project is just using .Net 3.5 .

Does anyone know why this setting was changed? I am suspecting that a Windows Update for the .NET Framework might have caused this. It took quite some time to figure this out, so I would like know what the actual cause was and how I can prevent it from happening again.

For those of you who should stumble upon this and have the same problem, it can be easily fixed (tested in Visual Studio 2012 and InstallShield LE). Run Visual Studio as admin and go to the InstallShield LE tab. Select "Options" and go to the ".NET" tab. Now select the correct path for your .NET Framework according to the version you use in your project.

Upvotes: 0

Views: 302

Answers (1)

Christopher Painter
Christopher Painter

Reputation: 55601

You said it yourself, the (in)famous 1001 error. Do yourself a favor and switch to WiX ToolSet's Deployment Tools Foundation (DTF) managed custom actions. You can encapsulate this in a WiX merge module project and then consume the merge module in your InstallShield LE project. It's such a better design pattern.

One of the really nice things about DTF is you can compile a custom action for .NET 2.0 and include a CustomAction.Config that allows it to bind to CLR 2.0 or 4.0. This makes it practically bulletproof from XP to Windows 10.

Aren't your users important enough to make sure they never see a 1001 error? Isn't your help desk important enough to make sure they don't get those calls? Isn't your brand important enough to make sure that users don't post your product sucks on social media?

Upvotes: 1

Related Questions