We have two Projects, A and B. There is a file in ProjectB that needs to be run by ProjectA. Originally thinking that ProjectB was a "child" of ProjectA I wrote some code that included the lines:
<CustomAction Id="ResetProjectBDir" Property="PROJECTBDIR" Value="[SourceDir]\PROJECTBDIR" /> <CustomAction Id="RunBFile" Directory="PROJECTBDIR" ExeCommand='[PROJECTBDIR]file.exe ' Return="asyncNoWait" /> That worked fine, and to show a "random" example from the install log right after CostFinalize, resulted in: PROPERTY CHANGE: Modifying PROJECTBDIR property. Its current value is 'C:\Documents and Settings\gfinger\Desktop\Install\\PROJECTBDIR'. Its new value: 'C:\Documents and Settings\gfinger\Desktop\Install\PROJECTBDIR\'. However then I was informed that ProjectB was actually a "sibling" of ProjectA, and their install folders would be at the same level, along with some other "sibling" projects that would also need to access ProjectB in the same manner. So I changed the above to: <CustomAction Id="ResetProjectBDir" Property="PROJECTBDIR" Value="[SourceDir]..\PROJECTBDIR" /> However now when I try to run it I get: Product: Project A -- Error 1324. The folder path '..' contains an invalid character. Is there some way to fix the Custom Action so it will work properly? Or some other way to access a folder that's above SourceDir in the folder hierarchy? Thanks! ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
