Richard,

This should work just fine. Please send me a zip file containing the minimum set of files necessary to reproduce this issue.

Thanks,

Gert

----- Original Message ----- From: "Richard Sbarro" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 24, 2004 10:46 PM
Subject: [Nant-users] Globalized resources with Nant...



I'm having a problem using the csc task to compile a resources file for
my solution. I'm using the nant nightly build from 8/4/2004 (0.85.1677.0).


Basically, when I reflect the resources file created from a VS.NET using
Lutz Roeder's Reflector tool <http://www.aisto.com/roeder/dotnet/>, I
see the namespace of the resource reflected as
"MyProject.MyResources.en-US.resources".

<csc output="Build\MyProject.exe" target="winexe">
   <references basedir="Build">
       <include
name="C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Microsoft.*.dll" />
       ...
   </references>
   <sources basedir=".">
       <include name="MyProject\**\*.cs" />
   </sources>
   <resources prefix="MyProject.MyResources" dynamicprefix="false">
       <include name="MyProject\Definitions\**\*.resources" />
   </resources>
</csc>

However, when I use the above code in my Nant build, it creates a
.resources.dll, but the namespace is changed to
"MyProject.MyResources.resources".  When I run the executable, it can't
pick up the values in the resources dll, and I'm assuming that's because
the "en-US" is left off the namespace.  Is there a problem with handling
globalized resources in the csc task, or am I just missing something...?

Thanks,
Rich




------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to