Re: [WiX-users] Question about $(Platform) in Votive Output name
Please file a feature request. Even better, contributing a fix would be much appreciated. > Date: Tue, 27 Aug 2013 07:18:38 -0700 > From: techsupport...@gmail.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Question about $(Platform) in Votive Output name > > This still seems to be the case in 3.7.1224.0 > I'd like to be able to use MSBuild variables in the output name as > everything else works with my current project expect this. Currently I > either have to duplicate my project wixproj file and 'hard code' the name in > the UI or bypass the UI and edit the xml myself. I'd like to use the votive > UI! (I realize it's a minor issue as there is a workaround, but it's > confusing for a wixproj/votive newbie). > Thanks > Matt > > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Question-about-Platform-in-Votive-Output-name-tp709453p7588469.html > Sent from the wix-users mailing list archive at Nabble.com. > > -- > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about $(Platform) in Votive Output name
This still seems to be the case in 3.7.1224.0 I'd like to be able to use MSBuild variables in the output name as everything else works with my current project expect this. Currently I either have to duplicate my project wixproj file and 'hard code' the name in the UI or bypass the UI and edit the xml myself. I'd like to use the votive UI! (I realize it's a minor issue as there is a workaround, but it's confusing for a wixproj/votive newbie). Thanks Matt -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Question-about-Platform-in-Votive-Output-name-tp709453p7588469.html Sent from the wix-users mailing list archive at Nabble.com. -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about $(Platform) in Votive Output name
I didn't figure it would, but thought it was worth asking. :-) Thanks. Chris On Thu, Jun 26, 2008 at 5:18 PM, Jason Ginchereau <[EMAIL PROTECTED]> wrote: > The change applies only to WiX projects, and could not possibly affect > escaping behavior in non-WiX projects. > > Most of the WiX project code is shared between VS2005 and VS2008, including > this part. > > -Original Message- > From: [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] On Behalf Of Christopher Karper > Sent: Thursday, June 26, 2008 11:40 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Question about $(Platform) in Votive Output name > > This may seem like a silly question, but is this change global? Now my > output paths are exhibiting the same escaping behavior, for non WiX > projects. > Was this a change in 2008, or did your change have other effects? > > Chris > > On Wed, Jun 25, 2008 at 1:42 PM, Jason Ginchereau <[EMAIL PROTECTED]> > wrote: > > > >>I'd rather see it not escaped, but that's just me. I don't even know > if > > that's a WiX thing, or a VS2008 thing. > > Auto-escaping special chars is a recent change I implemented in the > Votive > > properties dialogs. It is intended to prevent one from getting into a > state > > where the project file can't be loaded, or is loaded incorrectly, because > > special characters can unintentionally confuse the parser. > > > > So, certain MSBuild special characters are auto-escaped as a %hex code > when > > they are entered in the properties dialogs. But the $() characters should > > not be escaped for properties that support MSBuild variables. Currently > > those are: > >Compiler/Linker/Lib Additional Options > >Preprocessor Variables > >WiX Variables > >Output Path > >Pre/Post Build Event > > > > Output Name is not in that list, but it probably should be. I agree with > > your feedback that the Output Name value should allow embedded MSBuild > > variables. > > > > -Jason- > > > > -Original Message----- > > From: [EMAIL PROTECTED] [mailto: > > [EMAIL PROTECTED] On Behalf Of Christopher Karper > > Sent: Wednesday, June 25, 2008 10:17 AM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Question about $(Platform) in Votive Output name > > > > So, here's the part where I answer my own question. Sheepishly, I have > to > > admit that when I changed the .wixproj file by hand, I put in ($Platform) > > instead of $(Platform).. So, once that was corrected, I got the behavior > I > > was looking for. > > > > The fact remains that the 2008 version seems to be escaping the non > > alphanumeric characters, but whether you consider that a bug or a feature > > is > > up to you, I guess. I'd rather see it not escaped, but that's just me. > > I > > don't even know if that's a WiX thing, or a VS2008 thing. > > > > Chris > > > > On Wed, Jun 25, 2008 at 1:00 PM, Christopher Karper < > > [EMAIL PROTECTED]> wrote: > > > > > In a project I created in VS2005 I used "Installer $(Platform)" as my > > > output name... It worked fine by created "Installer x64.msi" > > > > > > Now, I've converted to VS2008, and it still works fine. > > > > > > However, I created a new project, and set up a merge module WiX > project, > > > with "Module $(Platform)" as the output name, and it creates "Module > > > $(Platform).msm" as the output. > > > > > > In the .wixproj XML, I noticed it had escaped the $() characters, so I > > > replaced those manually and reopened it, but to no avail. It's still > > > creating the name without replacement. > > > > > > Is this a change in platform functionality? Was I relying on a bug > that > > > was fixed? Is this a bug that was introduced? Am I a great big fat > > idiot? > > > Any and all advice would be appreciated. :-) > > > > > > Thanks! > > > Chris > > > > > > > > > > > - > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > http://sourceforge.net/services/buy/index.php > > ___ > > WiX-users mailing
Re: [WiX-users] Question about $(Platform) in Votive Output name
The change applies only to WiX projects, and could not possibly affect escaping behavior in non-WiX projects. Most of the WiX project code is shared between VS2005 and VS2008, including this part. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Thursday, June 26, 2008 11:40 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Question about $(Platform) in Votive Output name This may seem like a silly question, but is this change global? Now my output paths are exhibiting the same escaping behavior, for non WiX projects. Was this a change in 2008, or did your change have other effects? Chris On Wed, Jun 25, 2008 at 1:42 PM, Jason Ginchereau <[EMAIL PROTECTED]> wrote: > >>I'd rather see it not escaped, but that's just me. I don't even know if > that's a WiX thing, or a VS2008 thing. > Auto-escaping special chars is a recent change I implemented in the Votive > properties dialogs. It is intended to prevent one from getting into a state > where the project file can't be loaded, or is loaded incorrectly, because > special characters can unintentionally confuse the parser. > > So, certain MSBuild special characters are auto-escaped as a %hex code when > they are entered in the properties dialogs. But the $() characters should > not be escaped for properties that support MSBuild variables. Currently > those are: >Compiler/Linker/Lib Additional Options >Preprocessor Variables >WiX Variables >Output Path >Pre/Post Build Event > > Output Name is not in that list, but it probably should be. I agree with > your feedback that the Output Name value should allow embedded MSBuild > variables. > > -Jason- > > -Original Message- > From: [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] On Behalf Of Christopher Karper > Sent: Wednesday, June 25, 2008 10:17 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Question about $(Platform) in Votive Output name > > So, here's the part where I answer my own question. Sheepishly, I have to > admit that when I changed the .wixproj file by hand, I put in ($Platform) > instead of $(Platform).. So, once that was corrected, I got the behavior I > was looking for. > > The fact remains that the 2008 version seems to be escaping the non > alphanumeric characters, but whether you consider that a bug or a feature > is > up to you, I guess. I'd rather see it not escaped, but that's just me. > I > don't even know if that's a WiX thing, or a VS2008 thing. > > Chris > > On Wed, Jun 25, 2008 at 1:00 PM, Christopher Karper < > [EMAIL PROTECTED]> wrote: > > > In a project I created in VS2005 I used "Installer $(Platform)" as my > > output name... It worked fine by created "Installer x64.msi" > > > > Now, I've converted to VS2008, and it still works fine. > > > > However, I created a new project, and set up a merge module WiX project, > > with "Module $(Platform)" as the output name, and it creates "Module > > $(Platform).msm" as the output. > > > > In the .wixproj XML, I noticed it had escaped the $() characters, so I > > replaced those manually and reopened it, but to no avail. It's still > > creating the name without replacement. > > > > Is this a change in platform functionality? Was I relying on a bug that > > was fixed? Is this a bug that was introduced? Am I a great big fat > idiot? > > Any and all advice would be appreciated. :-) > > > > Thanks! > > Chris > > > > > > > - > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > - > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - Check out the new SourceForge.net Marketplace. It'
Re: [WiX-users] Question about $(Platform) in Votive Output name
This may seem like a silly question, but is this change global? Now my output paths are exhibiting the same escaping behavior, for non WiX projects. Was this a change in 2008, or did your change have other effects? Chris On Wed, Jun 25, 2008 at 1:42 PM, Jason Ginchereau <[EMAIL PROTECTED]> wrote: > >>I'd rather see it not escaped, but that's just me. I don't even know if > that's a WiX thing, or a VS2008 thing. > Auto-escaping special chars is a recent change I implemented in the Votive > properties dialogs. It is intended to prevent one from getting into a state > where the project file can't be loaded, or is loaded incorrectly, because > special characters can unintentionally confuse the parser. > > So, certain MSBuild special characters are auto-escaped as a %hex code when > they are entered in the properties dialogs. But the $() characters should > not be escaped for properties that support MSBuild variables. Currently > those are: >Compiler/Linker/Lib Additional Options >Preprocessor Variables >WiX Variables >Output Path >Pre/Post Build Event > > Output Name is not in that list, but it probably should be. I agree with > your feedback that the Output Name value should allow embedded MSBuild > variables. > > -Jason- > > -Original Message- > From: [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] On Behalf Of Christopher Karper > Sent: Wednesday, June 25, 2008 10:17 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Question about $(Platform) in Votive Output name > > So, here's the part where I answer my own question. Sheepishly, I have to > admit that when I changed the .wixproj file by hand, I put in ($Platform) > instead of $(Platform).. So, once that was corrected, I got the behavior I > was looking for. > > The fact remains that the 2008 version seems to be escaping the non > alphanumeric characters, but whether you consider that a bug or a feature > is > up to you, I guess. I'd rather see it not escaped, but that's just me. > I > don't even know if that's a WiX thing, or a VS2008 thing. > > Chris > > On Wed, Jun 25, 2008 at 1:00 PM, Christopher Karper < > [EMAIL PROTECTED]> wrote: > > > In a project I created in VS2005 I used "Installer $(Platform)" as my > > output name... It worked fine by created "Installer x64.msi" > > > > Now, I've converted to VS2008, and it still works fine. > > > > However, I created a new project, and set up a merge module WiX project, > > with "Module $(Platform)" as the output name, and it creates "Module > > $(Platform).msm" as the output. > > > > In the .wixproj XML, I noticed it had escaped the $() characters, so I > > replaced those manually and reopened it, but to no avail. It's still > > creating the name without replacement. > > > > Is this a change in platform functionality? Was I relying on a bug that > > was fixed? Is this a bug that was introduced? Am I a great big fat > idiot? > > Any and all advice would be appreciated. :-) > > > > Thanks! > > Chris > > > > > > > - > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > - > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about $(Platform) in Votive Output name
>>I'd rather see it not escaped, but that's just me. I don't even know if >>that's a WiX thing, or a VS2008 thing. Auto-escaping special chars is a recent change I implemented in the Votive properties dialogs. It is intended to prevent one from getting into a state where the project file can't be loaded, or is loaded incorrectly, because special characters can unintentionally confuse the parser. So, certain MSBuild special characters are auto-escaped as a %hex code when they are entered in the properties dialogs. But the $() characters should not be escaped for properties that support MSBuild variables. Currently those are: Compiler/Linker/Lib Additional Options Preprocessor Variables WiX Variables Output Path Pre/Post Build Event Output Name is not in that list, but it probably should be. I agree with your feedback that the Output Name value should allow embedded MSBuild variables. -Jason- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Wednesday, June 25, 2008 10:17 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Question about $(Platform) in Votive Output name So, here's the part where I answer my own question. Sheepishly, I have to admit that when I changed the .wixproj file by hand, I put in ($Platform) instead of $(Platform).. So, once that was corrected, I got the behavior I was looking for. The fact remains that the 2008 version seems to be escaping the non alphanumeric characters, but whether you consider that a bug or a feature is up to you, I guess. I'd rather see it not escaped, but that's just me. I don't even know if that's a WiX thing, or a VS2008 thing. Chris On Wed, Jun 25, 2008 at 1:00 PM, Christopher Karper < [EMAIL PROTECTED]> wrote: > In a project I created in VS2005 I used "Installer $(Platform)" as my > output name... It worked fine by created "Installer x64.msi" > > Now, I've converted to VS2008, and it still works fine. > > However, I created a new project, and set up a merge module WiX project, > with "Module $(Platform)" as the output name, and it creates "Module > $(Platform).msm" as the output. > > In the .wixproj XML, I noticed it had escaped the $() characters, so I > replaced those manually and reopened it, but to no avail. It's still > creating the name without replacement. > > Is this a change in platform functionality? Was I relying on a bug that > was fixed? Is this a bug that was introduced? Am I a great big fat idiot? > Any and all advice would be appreciated. :-) > > Thanks! > Chris > > > - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about $(Platform) in Votive Output name
Ah escaping. I'm not sure if it's a VS2008 vs. Votive thing either, but if you want to take a test to see how painful figuring out what to escape can be, see the following blog entries on how VS/MSBuild handle things: http://blogs.msdn.com/msbuild/archive/2005/10/27/484742.aspx http://blogs.msdn.com/msbuild/archive/2005/10/31/484750.aspx http://blogs.msdn.com/msbuild/archive/2005/11/01/484754.aspx Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Wednesday, June 25, 2008 10:17 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Question about $(Platform) in Votive Output name So, here's the part where I answer my own question. Sheepishly, I have to admit that when I changed the .wixproj file by hand, I put in ($Platform) instead of $(Platform).. So, once that was corrected, I got the behavior I was looking for. The fact remains that the 2008 version seems to be escaping the non alphanumeric characters, but whether you consider that a bug or a feature is up to you, I guess. I'd rather see it not escaped, but that's just me. I don't even know if that's a WiX thing, or a VS2008 thing. Chris On Wed, Jun 25, 2008 at 1:00 PM, Christopher Karper < [EMAIL PROTECTED]> wrote: > In a project I created in VS2005 I used "Installer $(Platform)" as my > output name... It worked fine by created "Installer x64.msi" > > Now, I've converted to VS2008, and it still works fine. > > However, I created a new project, and set up a merge module WiX project, > with "Module $(Platform)" as the output name, and it creates "Module > $(Platform).msm" as the output. > > In the .wixproj XML, I noticed it had escaped the $() characters, so I > replaced those manually and reopened it, but to no avail. It's still > creating the name without replacement. > > Is this a change in platform functionality? Was I relying on a bug that > was fixed? Is this a bug that was introduced? Am I a great big fat idiot? > Any and all advice would be appreciated. :-) > > Thanks! > Chris > > > - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about $(Platform) in Votive Output name
I appreciate your time, and I'm sorry you got to it before I discovered my typo. :-\ Chris On Wed, Jun 25, 2008 at 1:16 PM, Neil Enns <[EMAIL PROTECTED]> wrote: > I just gave this a try with a clean Votive project by manually editing the > .wixproj file to add $(Project) to the output name and it worked fine. > Here's what my MSBuild property looks like: > >WixMergeModule1 $(Platform) > > This is with WiX 3.0.4022.0. > > Can you send out what your Property blob at the top of the project file > looks like? > > Neil > > -Original Message- > From: [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] On Behalf Of Christopher Karper > Sent: Wednesday, June 25, 2008 10:00 AM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Question about $(Platform) in Votive Output name > > In a project I created in VS2005 I used "Installer $(Platform)" as my > output > name... It worked fine by created "Installer x64.msi" > > Now, I've converted to VS2008, and it still works fine. > > However, I created a new project, and set up a merge module WiX project, > with "Module $(Platform)" as the output name, and it creates "Module > $(Platform).msm" as the output. > > In the .wixproj XML, I noticed it had escaped the $() characters, so I > replaced those manually and reopened it, but to no avail. It's still > creating the name without replacement. > > Is this a change in platform functionality? Was I relying on a bug that > was > fixed? Is this a bug that was introduced? Am I a great big fat idiot? > Any > and all advice would be appreciated. :-) > > Thanks! > Chris > - > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > - > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about $(Platform) in Votive Output name
So, here's the part where I answer my own question. Sheepishly, I have to admit that when I changed the .wixproj file by hand, I put in ($Platform) instead of $(Platform).. So, once that was corrected, I got the behavior I was looking for. The fact remains that the 2008 version seems to be escaping the non alphanumeric characters, but whether you consider that a bug or a feature is up to you, I guess. I'd rather see it not escaped, but that's just me. I don't even know if that's a WiX thing, or a VS2008 thing. Chris On Wed, Jun 25, 2008 at 1:00 PM, Christopher Karper < [EMAIL PROTECTED]> wrote: > In a project I created in VS2005 I used "Installer $(Platform)" as my > output name... It worked fine by created "Installer x64.msi" > > Now, I've converted to VS2008, and it still works fine. > > However, I created a new project, and set up a merge module WiX project, > with "Module $(Platform)" as the output name, and it creates "Module > $(Platform).msm" as the output. > > In the .wixproj XML, I noticed it had escaped the $() characters, so I > replaced those manually and reopened it, but to no avail. It's still > creating the name without replacement. > > Is this a change in platform functionality? Was I relying on a bug that > was fixed? Is this a bug that was introduced? Am I a great big fat idiot? > Any and all advice would be appreciated. :-) > > Thanks! > Chris > > > - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about $(Platform) in Votive Output name
I just gave this a try with a clean Votive project by manually editing the .wixproj file to add $(Project) to the output name and it worked fine. Here's what my MSBuild property looks like: WixMergeModule1 $(Platform) This is with WiX 3.0.4022.0. Can you send out what your Property blob at the top of the project file looks like? Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Wednesday, June 25, 2008 10:00 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Question about $(Platform) in Votive Output name In a project I created in VS2005 I used "Installer $(Platform)" as my output name... It worked fine by created "Installer x64.msi" Now, I've converted to VS2008, and it still works fine. However, I created a new project, and set up a merge module WiX project, with "Module $(Platform)" as the output name, and it creates "Module $(Platform).msm" as the output. In the .wixproj XML, I noticed it had escaped the $() characters, so I replaced those manually and reopened it, but to no avail. It's still creating the name without replacement. Is this a change in platform functionality? Was I relying on a bug that was fixed? Is this a bug that was introduced? Am I a great big fat idiot? Any and all advice would be appreciated. :-) Thanks! Chris - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
