We have a project with quite a few embedded non-resx resource files at different
folder depths. The prefix attribute does not correctly mimic the VS.NET behavior for
generating manifest resource names.
We have made a small change to the source to add a dynamicprefix boolean attribute.
When set to true, the manifest resource name is generated by:
[prefixAttribute].[filePathRelativeToBaseDir].[filename]
An example appears below.
Is this behavior useful to anyone else? Is it useful to patch into CVS? If so, maybe
someone could point me to instructions on how to make the contribution to the project.
Thanks!
Jason Pettys
An example to illustrate:
Including the following resources element:
<resources basedir="c:\code\myproj" prefix="myproj" dynamicprefix="true">
<includes name="**/*.txt">
</resources>
Against the following files:
c:\code\myproj\readme.txt
c:\code\myproj\help\index.txt
c:\code\myproj\help\chap01\page.txt
Will produce manifest resource names:
myproj.readme.txt
myproj.help.index.txt
myproj.help.chap01.page.txt
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
