RE: [nant-dev] ResourceUtil rewind

Greco Giuseppe wrote: what's about something like that? Giving the following resource files Global.resx Another.resx ... .resx we could have a separate resource manager for each resource file, This means storing *all* the resources in a single assembly I don't

[nant-dev] ResourceUtil rewind

Hi Ian, what's about something like that? Giving the following resource files Global.resx Another.resx ... .resx we could have a separate resource manager for each resource file, solving also the problem with VS.NET: using System.Reflection; using System.Resources; using

[nant-dev] ResourceUtils

Hi Ian, I think it would be preferable to have a common resource assembly (e.g. NAnt.Resources.dll). Letting an assembly access resources of another assembly and viceversa is not that elegant. Moreover, it would be difficult to maintain messages consistently. There are also performance issues;

RE: [nant-dev] L16N - resx files

How about somthing like 'NA1001' for errors and warnings. !--Build Error Strings -- data name=NA1001 valueCould not find a '{0}' file in '{1}'/value commentSome descriptive comment/comment /data What about this? Could be a valid alternative? Error messages: data

RE: [nant-dev] L16N - resx files

Hmm - well I'd like the keep the number in there - for errors/warnings at least. It will make finding the use of a given error message easier later on. Okay, but tell me which one of the following formats: data name=NA1001 valueCould not find a '{0}' file in '{1}'/value

RE: [nant-dev] L16N

Hi Ian, looks like the xmldoc attribute you mention in a later email is the way to get around this. We would invoke ndoc once for each translated language. Exactly... although we should be able to knock up a script to generate stubs based on the original english doc. Of course...

RE: [nant-dev] ndoc task

Ian, sounds like a good idea. Why don't you log a bug for it ? Done. j3d. -- DISCLAIMER -- This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify

RE: [nant-dev] L16N

Ian, looks ok - but why not get AssemblyName dynamically using : Assembly.GetCallingAssembly() ? then you only need to define the RM class once in NAnt.Core. It depends if you plan to create separate resource files for the different NAnt assemblies. Furthermore, it depends also if you

RE: [nant-dev] L16N

Ian, looks ok - but why not get AssemblyName dynamically using : Assembly.GetCallingAssembly() ? then you only need to define the RM class once in NAnt.Core. You're right... attached to this email you'll find a better version of RM.cs (RM stands for [R]esource[M]anager). Let me know if it

RE: [nant-dev] L16N

Ian, You're right... attached to this email you'll find a better version of RM.cs (RM stands for [R]esource[M]anager). I figured that one out :). We could probably call it NAnt.Core.ResourceUtils or somthing like that. That's up to you... but such a name is a little bit too long

RE: [nant-dev] L16N

Ian, I'm at work too... so I cannot start right now... j3d. -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: mercoledì, 16 febbraio 2005 08:40 To: Greco Giuseppe Cc: nant-developers@lists.sourceforge.net Subject: Re: [nant-dev] L16N The first step would

RE: [nant-dev] L16N

csc ... ... resources include name=*.resx/ /resources /csc will work just fine. Just a question: does the resource element automatically embed the defalut resources into the assembly, or is the arg element still necessary? csc ... arg

[nant-dev] ndoc task

Hi all, Why doesn't the ndoc task support the NDoc argument xmldoc (see http://ndoc.sourceforge.net/usersguide.html)? NAnt assumes that XML files generated by the C# compiler are always located in the same directory as the compiled assemblies. Don't you think that we should add the xmldoc

[nant-dev] Fileset references

Title: Fileset references Hi all, does anybody know how far is the implementation of fileset refereces? (see www.mail-archive.com/[EMAIL PROTECTED]/msg01418.html for more info) Gius_. Giuseppe Greco T-Systems CS AG Birkenstrasse 21 8306 Brüttisellen Phone: +41 (0) 1 805 57 20 Fax:

[nant-dev] install target

Title: install target Hi all, It would be nice to have an install target in NAnt.build, so one could just type 'nant install' or 'nant linux install' to install NAnt. Here's my proposal: 1. Create a new install.config property set to win32 by default property name=install.config

RE: [nant-dev] Problems with basedir beginning with ../

, Gius_. -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 11, 2003 6:28 AM To: Greco Giuseppe Cc: Giuseppe Greco; NAnt Developers Subject: Re: [nant-dev] Problems with basedir beginning with ../ does it work if you specify the full path

[nant-dev] RE: [Nant-users] docbook.xsl and nant

) and let NAnt validate XML documents using the XMLValidatingReader class. Gius_. -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 10, 2003 9:44 AM To: Greco Giuseppe Cc: 'Jaroslaw Kowalski'; [EMAIL PROTECTED] Subject: Re: [Nant-users] docbook.xsl

RE: [nant-dev] cvs re-org

Title: RE: [nant-dev] cvs re-org Great! Have the pending patches been included (e.g. bug-fix in the exec task)? I included them in my local copy of NAnt last week, so I need to know if I have to include them again... Gius_. -Original Message- From: Ian MacLean

RE: [nant-dev] NAnt CVS Directories

Title: RE: [nant-dev] NAnt CVS Directories wouldn't it be possible to check if a buildfile exists in directory (using the available task with an if task) ? In my opinion, the exclude property has too limited usability what will happen if you want to exclude two directories ?