Page 1 of 1

MSI Error with two projects sharing the same files

Posted: Mon Aug 31, 2009 4:08 pm
by ulrichard
Hi,

I have two installer projects that share the same files (scripts, dialogs, translations...).
I know, it's not exactly how it was thought, but if I get it to work one way or another, it would save me a lot of maintenance work.
The different variations are built by passing different compiler variables to miabuild and in the second case calling a different project file (FinalBuilder).

Pre conditions
ApplicationGUID and version have been compiler variables for a while without any problems so far.
But populating the ProductName from a compiler variable seems to be a different story...

Attempt 1
My first try was to have only one project and use a compiler variable to set the ProductName. I renamed the mtx files to #ProductName#.mtx and it seemed to work. But the language selection dialog often didn't appear and the LANGUAGE variable was not set, thus all the dialogs and text appeared in english. None of the language dependent files were installed.
In the script I have a couple of [Compiler if #ProductName# = 3D]

Attempt 2
So, I copied all the files to another folder (say from 2D to 3D), and changed the ProductName in the project file along with the mtx file name.
In the script I canged the conditionals to [Compiler if #TITLE# = 3D]
Now the language selection dialog always appears and the dialogs appear in the selected language. The language dependent files get installed.
Now here comes the strange part.
If I install 3D and then 2D, everything is fine.
But if I install 2D and then 3D, Windows installer displays an empty error message and quits. In the msi log I found the following errorcodes that I found on http://msdn.microsoft.com/en-us/library ... 85%29.aspx but the description didn't tell me much:
1708, 1709, 1603, 4010

Any Ideas or hints?
Richard

Posted: Tue Sep 01, 2009 2:25 pm
by neillans
Hi Richard,

This is an interesting scenerio, however, not something we would support I am afraid !

But ... anyway :)

I would suggest creating two seperate projects - and then moving all your logic into seperate script files.
Finally, use the INCLUDE SCRIPT statements to load the script files into each project.

Good Luck!

Re: MSI Error with two projects sharing the same files

Posted: Tue Mar 23, 2010 2:03 am
by SergiiGulenok
Now here comes the strange part.
If I install 3D and then 2D, everything is fine.
But if I install 2D and then 3D, Windows installer displays an empty error message and quits. In the msi log I found the following errorcodes that I found on http://msdn.microsoft.com/en-us/library ... 85%29.aspx but the description didn't tell me much:
1708, 1709, 1603, 4010
I have the same problem. In my case I think that it is occured because of common merged modules that are used for both installers. Could it really be the case? Why this error occurs only when installing 3D after 2D but not when installing in opposite sequence?