Main install is 32 bit and includes a few 32-bit projects.
Chained (secondary) install is built as x64 target by VS2008 Setup (.msi) and includes two 64-bit projects - this is a 64-bit driver and its custom action DLL.
I chained the above so that main install will launch the secondary install on 64-bit Win7.
The main install works and installs fine but secondary install is never launched.
The same main installs launches 32-bit secondary install (same driver) on 32-bit XP without problem.
Any clues, how do I chain 64-bit setup to main 32-bit setup to make it work on 64bit Win7?
Running secondary installer (64-bit) stand-alone on WIn7 b4 bit works fine as well.
Mihai, I looked at the articles - there ws nothing there that I didn't already take into account. My secondary install is preconditioned to execute only on x64 machines (by VersionNT64). I also added Windows Installer 4.5 as a prerequisite.
The problem is somewhere else - I can see that the secondary package is launched and starts executing... then it simply ralls back...
When I look at the log file I see this:
"CustomAction ProviderInstall.dll returned actual error code 1603 (note that this may not be 100% accurate...)."
My understanding is that this is some kind of security/priviledge error (?)
I am admin on this machine and also run this "Run as Admininstrator". Still though I am not sure with what privileges the main install executes the secondary install - that is, if the secondary inherite all the admin privileges of the first.
My secondary package is an install of the driver (special TAPI driver that does not have .INI file). Instead it has a helper, ProviderInstall.dll, which is a custom actions DLL that has Install and Uninstall functions exposed.
BTW, as I mentioned: the second package works fine when I execute it by itself, but I still need to chain it.
I am using your trail version and the project is defined as urgent - I am looking into purchasing it once I am convinced that I can solve this problem - it is the last hurdle left before I can tell to management - "buy it". Therefore, I'd appreciate your attention.
Meanwhile, I am trying something different that does not include chained install.
I removed chained install from the main package and added two 64-bit files to what AI calls System64 - according to my understanding it is \windows\system32 folder.
the install runs but these two files are always copied to Windows\SystemWOW64 folder, no matter if I put them in AI System and System64 folders...
It is a 64-bit package that deploys 32-bit modules and now I am trying to simply copy 2 64-bit files to the right place, and it does not work...How come?
FOLLOW US
Get the latest news in Application Packaging