The commonly accepted solution is breaking up the code into fragments. The
source code of WiX UI (wixui.wixlib) might be of your interest, as it is a
good example (I think, what I write at least stands for WiX 2.x).
In this case, for each level of UI - depending on how far it is reduced
- different dialog collections are obtained from the same dialogs using
DialogRef elements (each dialog is in a separate WiX file, and there is one
another "atomic" file for the binaries like bitmaps).
2007/10/17, Sajo Jacob <[EMAIL PROTECTED]>:
>
> I am a newbie with WiX. I had a quick question regarding structuring my
> WiX wxs file. The way I have it set up is that all the UI code is in this
> one large .WXS file. I was wondering if I could break up this WXS file into
> smaller files (maybe like each UI Dialog in its own file or something) so
> that changes can be multiple developers can work on different areas
> simultaneously.
> Appreciate your help.
> Thanks,
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
