I'm guessing that you are declaring a property in a merge module and trying 
to use it in the installer.  The merge module will append a .GUID to the 
property name unless you give it set the SuppressModularization attribute.  
Alternatively you can use the correct property name including .GUID in your 
installer.

----------------------------------------

From: "Erkan Celme" <ece...@discovertechnologies.com>

Sent: Monday, April 16, 2012 2:42 PM

To: "General discussion for Windows Installer XML toolset." 
<wix-users@lists.sourceforge.net>

Subject: Re: [WiX-users] Escaping brackets [ ] in merge modules (MSM)


I'm not sure what you mean by that. " Merge Modules append the Module/@Id 
to all identifiers."


Which identifiers? How is that breaking the escape characters? Could you 
please elaborate?


Thanks in advance

Erkan Celme

Phone: 312-927-5180


-----Original Message-----

From: Rob Mensching [mailto:r...@robmensching.com] 

Sent: Friday, April 13, 2012 11:24 PM

To: General discussion for Windows Installer XML toolset.

Subject: Re: [WiX-users] Escaping brackets [ ] in merge modules (MSM)


Merge Modules append the Module/@Id to all identifiers.


On Fri, Apr 13, 2012 at 8:39 AM, Erkan Celme < 
ece...@discovertechnologies.com> wrote:


> There are cases where I need to have brackets (square brackets) in 

> certain actions like running a SQL script that requires brackets or in 

> an XPath expression. You can escape them in a regular installer (MSI) 

> project by using [\[] or [\]], to open and close respectively. When I 

> do the same in a merge module, it doesn't work. For instance, if I 

> have a property called

> PROP1 with a value of "Value1", if I need, "[Value1]" as a literal, I 

> can do [\[][Value1][\]] and get what I need. However, in a merge 

> module, the same syntax produces an empty string. Does anyone have any 

> idea why it doesn't work the same way in a merge module? Any ideas on 

> how to work around this?

>

> Thanks in advance.

> Erkan

>

>

>

>

> ----------------------------------------------------------------------

> -------- For Developers, A Lot Can Happen In A Second.

> Boundary is the first to Know...and Tell You.

> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!

> http://p.sf.net/sfu/Boundary-d2dvs2

> _______________________________________________

> WiX-users mailing list

> WiX-users@lists.sourceforge.net

> https://lists.sourceforge.net/lists/listinfo/wix-users

>


--

virtually, Rob Mensching - http://RobMensching.com LLC

----------------------------------------------------------------------------
--

For Developers, A Lot Can Happen In A Second.

Boundary is the first to Know...and Tell You.

Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!

http://p.sf.net/sfu/Boundary-d2dvs2

_______________________________________________

WiX-users mailing list

WiX-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wix-users


----------------------------------------------------------------------------
--

For Developers, A Lot Can Happen In A Second.

Boundary is the first to Know...and Tell You.

Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!

http://p.sf.net/sfu/Boundary-d2dvs2

_______________________________________________

WiX-users mailing list

WiX-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to