Posted 09 May 2006 - 04:19
Posted 09 May 2006 - 13:35
Posted 17 May 2006 - 16:48
1) Don't have dependant modules. Have all modules directly referenced by the ISMergeModule table.
2) Do a "postbuild hack" where instead of associating the diretory tables in InstallShield you do an update on the Directory table post build and say set the Parent Directory to INSTALLDIR where DefaultDir = ".:Module Retarget......." You will also need to have an MSI SetProperty CA ( Type 51 ) sequenced after InstallInitialize to set TARGETDIR = INSTALLDIR so that any registry table entries and/or CustomActionData entries will point to the "correct" directory table entry.
Also beware, there is a bug in Visual Studio 2005 merge modules that I inquired about in another thread that no one ever replied to.
MSI Factory Provider for ADO.NET 2.0 (Work In Progress)
99 Bottles Of Beer - Windows Installer
PM for personal communication only. Please ask questions in the forums.
Posted 15 June 2006 - 18:44
Somebody knows the reason? pleasee..
Posted 16 June 2006 - 19:37
As far as I know MDAC is unrelated to Microsoft ActiveX Data Objects.