In the wix2010.targets I found CleanFile defined, so I could remap one
file, but further on I found this:

    <ReadLinesFromFile
File="$(IntermediateOutputPath)$(BindOutputsFilePrefix)%(CultureGroup.Identity)$(BindOutputsFileExtension)">
      <Output TaskParameter="Lines" ItemName="FileWrites"/>
    </ReadLinesFromFile>

    <CreateItem
Include="$(IntermediateOutputPath)$(BindContentsFilePrefix)%(CultureGroup.Identity)$(BindContentsFileExtension);$(IntermediateOutputPath)$(BindOutputsFilePrefix)%(CultureGroup.Identity)$(BindOutputsFileExtension);$(IntermediateOutputPath)$(BindBuiltOutputsFilePrefix)%(CultureGroup.Identity)$(BindBuiltOutputsFileExtension)">

      <Output TaskParameter="Include" ItemName="FileWrites" />
    </CreateItem>


    <ReadLinesFromFile
File="$(IntermediateOutputPath)$(BindContentsFilePrefix)%(CultureGroup.Identity)$(BindContentsFileExtension)">
      <Output TaskParameter="Lines" ItemName="_BindInputs" />
    </ReadLinesFromFile>

    <ReadLinesFromFile
File="$(IntermediateOutputPath)$(BindBuiltOutputsFilePrefix)%(CultureGroup.Identity)$(BindBuiltOutputsFileExtension)">
      <Output TaskParameter="Lines" ItemName="_BindBuiltOutputs" />
    </ReadLinesFromFile>

So those seems to be built on the fly, instead of getting assigned to an
property as is done with CleanFile..

Same with the Light task inside there:


BindContentsFile="$(IntermediateOutputPath)$(BindContentsFilePrefix)%(CultureGroup.Identity)$(BindContentsFileExtension)"

BindOutputsFile="$(IntermediateOutputPath)$(BindOutputsFilePrefix)%(CultureGroup.Identity)$(BindOutputsFileExtension)"

BindBuiltOutputsFile="$(IntermediateOutputPath)$(BindBuiltOutputsFilePrefix)%(CultureGroup.Identity)$(BindBuiltOutputsFileExtension)"






On Tue, Sep 16, 2014 at 6:41 PM, Asbjørn Mikkelsen <asbj...@neslekkim.net>
wrote:

> Hm, I added those in the same propertygroup as where OutputPath and
> IntermediateOutputPath is set, but nothing happens, it generates stil the
> same names
> Where are those properties listed?, like what is avalable?
>
> In this doc:
> http://wixtoolset.org/documentation/manual/v3/overview/light.html
> I cant even find the parameter that is fed to light for these files even?,
> like these parameters:
>
>  -contentsfile obj\<myprojectname>.wixproj.BindContentsFileListnb-NO.txt
>  -outputsfile obj\<myprojectname>.wixproj.BindOutputsFileListnb-NO.txt
>  -builtoutputsfile
> obj\<myprojectname>.wixproj.BindBuiltOutputsFileListnb-NO.txt
>
> and in the msbuild log, that is the only place I see those names listed..
>
>
>
> On Tue, Sep 16, 2014 at 6:00 PM, Rob Mensching <r...@firegiant.com> wrote:
>
>> PS: I just remembered, you can change the name of those files in your
>> .wixpproj by setting Properties like BindContentsFile, BindOutputsFile, etc.
>>
>> _____________________________________________________________
>>  Short replies here. Complete answers over there:
>> http://www.firegiant.com/
>>
>>
>> -----Original Message-----
>> From: Rob Mensching [mailto:r...@firegiant.com]
>> Sent: Monday, September 15, 2014 12:42 PM
>> To: General discussion about the WiX toolset.
>> Subject: Re: [WiX-users] LGHT0284: Support for more than 260 characthers
>> in Path?
>>
>> We could make those binder data file paths shorter in WiX v4.0.
>>
>> _____________________________________________________________
>>  Short replies here. Complete answers over there:
>> http://www.firegiant.com/
>>
>> ------------------------------------------------------------------------------
>> Want excitement?
>> Manually upgrade your production database.
>> When you want reliability, choose Perforce.
>> Perforce version control. Predictably reliable.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
>> _______________________________________________
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>
>
>
> --
> mvh
> Asbjørn
>



-- 
mvh
Asbjørn
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to