Are there best practices and recommendations for using AI to install an app which requires the .NET Framework 2.0 *and* Windows Installer 3.0? The installation of .NET FW 2.0 requires WI 3.0.
(Please see also this link http://www.advancedinstaller.com/forums ... php?t=1530 for contextual info and cross-reference.)
One scenario where this would manifest itself is when deploying a .NET 2.0 app to a Windows 2000 SP4 target machine. A Windows 2000 SP4 target machine may not have Windows Installer 3.0 on it. The installation of .NET FW 2.0 requires Windows Installer 3.0.
Although I cannot say for sure, my instincts tell me that this may get tricky because (a.) installation of WI 3.0 may require a system restart and (b.) installation of .NET FW 2.0 implies the use of WI so if we were to proceed with a custom action to perform the .NET FW 2.0 installation from within our own AI install, we may hit difficulties. There is a possibility that my instincts are wrong, and there is indeed a crisp, clean set of best practices for this deployment scenario.
My ultimate goal is to build a AI project which deploys WI 3.0 + .NET FW 2.0 + my app. My app does not require WI 3.0, nor does AI, but the .NET FW 2.0 does indeed.
Thank you for your time, and for a great product in AI.
FOLLOW US
Get the latest news in Application Packaging