Hi,
This is simply a warning to you to make sure that the conditions
are bulletproof, if you are sure, you can ignore it.
I would personally treat this as configuration, i.e. nothing to do with
the the installer. You could install all the report files in specific
folders and get the application to allow you to switch between them
(this is what we do with localized files). Of course you may not have
access to the application.
You could also install all the languages to a template folder then copy
the selected one with filecopy to the report location, this may add
unneeded complexity to the install though.
Dave
-----Original Message-----
From: Thomas Due [mailto:t...@scanvaegt.dk]
Sent: 26 May 2010 08:50
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Architectural advice needed
Hi,
I need a bit of advice on my installer from you guys.
I have an installer which is mostly done, several dozen files, some
windows services which is registered and started, etc.
However, during the interview I ask for a language which the
installation should use. This choice results in a set of different
report files being installed based on language.
As it is right now, I have each language report set isolated in separate
components, which is enabled/disabled based on the language choice made
during the interview.
However, since I cannot guarantee that the report files will have unique
names, I get a lot of ICE (ICE30 to be specific) warnings because there
are files with identical names and that these have the same destination.
The exact warning is: ICE30: The target file 'Articles.rdl' might be
installed in '[ProgramFilesFolder]\f252vad8\ScanX.NET\Reports\' by two
different conditionalized components on an SFN system:
'DA_ReportsComponent' and 'NO_ReportsComponent'. If the conditions are
not mutually exclusive, this will break the component reference counting
system.
Now, I am faced with an architectural challenge; how do I solve this
best?
1. In reality I could just ignore these warnings, as the conditions I
have set prevents more than one language-specific component from being
installed. But I abhor warning in my code, even if they have no
consequence.
2. Restructure the installer, so each language-specific component is
contained in a transform package, this has the extra advantage of
enabling me to localize the installation interview as well. It does,
however, require a bootstrapper.
3. Ignore the issue complete and distribute the report files as a zip
and letting the user / software technician install them manually after
the installation is complete.
4. ?
I would like some advice on how things like this is usually done.
Thank you,
Thomas Due
Software Developer
------------------------------------------------------------------------
------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
</pre>
<BR style="font-size:4px;">
<a href = "http://www.sdl.com";><img src="http://www.sdl.com/images/email
logo_150dpi-01.png" alt="www.sdl.com" border="0"/></a>
<BR>
<font face="arial" size="2" "><a href = "http://www.sdl.com";
style="color:005740; font-weight: bold">www.sdl.com</a>
<BR>
<BR>
<font face="arial" size="1" color="#736F6E">
<b>SDL PLC confidential, all rights reserved.</b>
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without acting upon or copying any of its contents, and we
further request that you advise us.<BR>
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.<BR>
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY,
UK.
</font>
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
