Re: [WiX-users] KeyPath problem that I do not understand

2009-09-17 Thread Bob Arnson
Dirk Ziegelmeier wrote: > 1) Did you see that I attached another error case to my bug report? It > may have the same root cause, but it look different from my "black-box > view". > Also fixed, same cause. > 2) Is there a chance this gets backported to V3.0 "SP1"? (nightly/weekly > build) >

Re: [WiX-users] KeyPath problem that I do not understand

2009-09-17 Thread Dirk Ziegelmeier
that this is fixed in > v3.5. > > -Original Message- > From: Dirk Ziegelmeier [mailto:d...@ziegelmeier.net] > Sent: Thursday, September 17, 2009 5:42 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] KeyPath problem that I do not understand &

Re: [WiX-users] KeyPath problem that I do not understand

2009-09-17 Thread Blair
I noticed (looking last night for something else) that this is fixed in v3.5. -Original Message- From: Dirk Ziegelmeier [mailto:d...@ziegelmeier.net] Sent: Thursday, September 17, 2009 5:42 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] KeyPath

Re: [WiX-users] KeyPath problem that I do not understand

2009-09-17 Thread Dirk Ziegelmeier
Hello Bob! done: Bug Id: 2860637 Thank you for your quick reply! I created a minimal file that reproduces the problem and attached it to the bug. For everyone who is interested:

Re: [WiX-users] KeyPath problem that I do not understand

2009-09-17 Thread Bob Arnson
Dirk Ziegelmeier wrote: > The line causing the error is " Name="[MergeRedirectFolder]ConstantNameB"..." so the problem seems to > be the property substitution in there. > *** But this RegistryValue is NOT the KeyPath of the component! *** > Please file a bug at SourceForge. -- sig://boB http:

Re: [WiX-users] KeyPath problem that I do not understand

2009-09-17 Thread Dirk Ziegelmeier
Hello again, my code fragment can even be simplified (no need for two "RegistryKey" entries):                         Dirk -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only devel

[WiX-users] KeyPath problem that I do not understand

2009-09-17 Thread Dirk Ziegelmeier
Hello all, I have the following code fragment in my merge module (Notice: Guid="*"):                                 The fragment above works. However, if I include the line that is commented out above, I get the following error: error LGHT0230 : The Component/@Guid attribute's value '

Re: [WiX-users] KeyPath problem

2007-08-09 Thread Patrice Lamarche
-users@lists.sourceforge.net Objet : RE: [WiX-users] KeyPath problem When no keypath is specified, it uses the first resource in the component. In your case it was the first file. In order to remove that file you need to remove the entire component. Note, that if you remove a component, you have

Re: [WiX-users] KeyPath problem

2007-08-08 Thread Peter Marcu
can be very tricky... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrice Lamarche Sent: Wednesday, August 08, 2007 8:42 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] KeyPath problem Hello, I'm working with a pat

[WiX-users] KeyPath problem

2007-08-08 Thread Patrice Lamarche
Hello, I'm working with a patch. I receive this error D:\Disk_X\Setup1.wxs(23) : error PYRO0243 : Component 'comment_protect_once.pl_1' has a changed keypath . Patches cannot change the keypath of a component. Here my wxs