PDA

View Full Version : DLL Hell, Windows Installer, .NET



BCastleman
04-12-2002, 10:14 AM
It was my understanding that one of the advantages of the Windows Installer paradigm was the elimination of DLL Hell by allowing product isolation during installation (Side-by-Side execution I believe is the terminology).

After reviewing Installshield docs, it appears that this is only a viable solution on Windows XP and requires utilization of the .Net framework.

Our primary reason for considering moving our installations to Developer 7 and Windows Installer technology would be this ability to tightly control the DLLs used by our application. But if it cannot be made backwards compatible to older OS's, then it is a futile effort.

Since both the .Net and Windows Installer frameworks can be installed on the older versions of Windows, is it possible to gain Side-By-Side execution through the family of Windows OS's?

Thanks,

Bob
SuccessWare Software

BruceJ
04-17-2002, 06:12 PM
I understand side-by-side component sharing is available in Windows 2000 and 98 Second Edition and later, not just XP. For more details, see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnw2k/html/sidebyside.asp.

At this stage I am unsure how, if at all, Developer 7 supports side-by-side component installation.

Art Middlekauff
04-23-2002, 01:47 PM
True Win32 application isolation is only available on Windows XP. This feature of XP is documented in MSDN (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sbscs/sxsstart_4i3p.asp). This form of isolcation does NOT require the use of .NET or the .NET Framework.

InstallShield Developer supports Win32 assemblies in the Components or Setup Design views.

Windows 2000 has a limited form of application isolation. This is supported in Developer via the Direct Editor which exposes the IsolatedComponent table.