Re: [WiX-users] public properties can be read inside the merge module?

2007-05-22 Thread Amit Srivastava (Tata Consultancy Services)
...? From: Amit Srivastava (Tata Consultancy Services) Sent: Monday, May 21, 2007 6:19 PM To: wix-users@lists.sourceforge.net Cc: Rob Mensching Subject: RE: public properties can be read inside the merge module? Any Suggestion…? From: Amit Srivastava (Tata

[WiX-users] FW: public properties can be read inside the merge module?

2007-05-21 Thread Amit Srivastava (Tata Consultancy Services)
Any help on this...? From: Amit Srivastava (Tata Consultancy Services) Sent: Monday, May 21, 2007 12:28 AM To: Rob Mensching Subject: RE: public properties can be read inside the merge module? Thanks for your quick response.. If we describe the properties inside the merge module then we can

Re: [WiX-users] public properties can be read inside the merge module?

2007-05-21 Thread Amit Srivastava (Tata Consultancy Services)
Any Suggestion...? From: Amit Srivastava (Tata Consultancy Services) Sent: Monday, May 21, 2007 12:03 PM To: 'wix-users@lists.sourceforge.net' Cc: Rob Mensching Subject: FW: public properties can be read inside the merge module? Any help on this...? From: Amit Srivastava (Tata Consultancy

[WiX-users] public properties can be read inside the merge module?

2007-05-20 Thread Amit Srivastava (Tata Consultancy Services)
Hi, I have created a merge module using wix and I am trying to read the public properties which is defined outside of merge module(i.e. inside the MSI file). Can we read that properties? That merge module is included in the main wix file file for creation the MSI. I am trying to read the

[WiX-users] error during linking the wix setup

2007-05-15 Thread Amit Srivastava (Tata Consultancy Services)
Hi, I am using the latest version of WIX3.0.2827.0 for creating the merge module. I am getting the linking error Error LGHT0102: The localization variable !(loc.msierrXmlFileFailedRead) is unknown. Please ensure the variable is defined. There are many more same type errors(Error LGHT0102).