Re: [nant-dev] Re: resource related changes (in .NET 2.0)

[Ian M. <ianm@ActiveState.com>]

Matthew Mastracci wrote:

> Gert Driesen wrote:
>
>> I've made an inventory of issue we need to tackle better soon than 
>> late, some of them have been discussed before, but I think its best 
>> to bring them up again in order to have an agreement (and solution) 
>> for all "issues" :
>>
>> 1. Resgen can be used to compile multiple resource files at once, and 
>> we already support this. However, we do not have a way to specifiy 
>> the output file for each individual resource file. This is not 
>> possible right now, as we use a fileset to specify the input 
>> resources, so the number of input files is not fixed. In some cases, 
>> using files matching a certain pattern is great, but in cases like 
>> this here, its a major PITA. Allowing multiple input files, and 
>> corresponding output files in a single run of the <resgen> task would 
>> be very good for the performance of the <solution> task ...  Are we 
>> gonna support this ? If we do : how ?
>
>
> What about multiple filesets for all of these cases?  I really liked 
> your suggestion for the <zip> task and I think it applies here equally 
> well.
>
> <resources>
> <resourcefileset target="foo.resource">
>   <includes ...>
> </>
> <resourcefileset target="foo2.resource">
>   <includes ...>
> </>
> </resources>

the trouble with this is that you still have to use the input file name 
as the name of the output resource file.  Unless you see the above 
example merging all the includes into a single file called foo.resource ?
I think what Gert is getting at is the ability to pass a 1:1 mapping of 
input files and resource names to resgen

fileA  : fileA.resources
fileB  :  resource_with_different_name_to_its_source_file.resources
...
correct me if I'm wrong.

btw the resoures fileset can already be specified multiple times - in 
order to use multiple prefix's. Its one of the few ( only ? ) case in 
NAnt currently where a fileset can be specified multiple times.

>
>> 2. We should support explicit manifest resource names to be specified 
>> for individual resources that need to be embedded/linked (using the 
>> compiler or al tasks)
>
>
This is another version of the same problem ie it requires a 1:1 mapping 
of input files to manifest resource names.

My take is that we will need some additional xml syntax to support this. 
There is no getting around that. Whether this takes the form of an 
entirely new element -or an extension of FileSet if what really needs to 
be decided. There were are couple of proposals in the thread that Gert 
included the end of. I'd post a link but MailArchive.com seems to be 
down roght now.

Ian