[nant-dev] FileSet

2003-09-09 Thread Martin Aliger
There is patch to support very nice feature as it is described in docs: FileSet. includes: comma-separated list of patterns of files that must be included Martin fileset.patch Description: Binary data

Re: [nant-dev] Another Solution Task suggestion

2003-09-09 Thread Martin Aliger
I don't like to use subdirectory of current path. Could be read only... Maybe we could add some attribute to do build instead of rebuild? Martin - Original Message - From: Eddie Tse [EMAIL PROTECTED] To: 'Erick Thompson' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday,

[nant-dev] documentation

2003-09-09 Thread Martin Aliger
I found more spots where doc leaks: 1/ FileSet. includes comma-separated list of patterns of files that must be included; all files are included when omitted. really? I want to use it and my hardly build comma-separated list throws: Error creating file set. ---

Re: [nant-dev] FileSet

2003-09-09 Thread Martin Aliger
PROTECTED] To: Martin Aliger [EMAIL PROTECTED]; ! nant [EMAIL PROTECTED] Sent: Tuesday, September 09, 2003 6:04 PM Subject: Re: [nant-dev] FileSet Just my personal opinion, but I'm not sure I like this ... It is just a personal preference, I do know Ant supports it (but I don't think it's used

Re: [nant-dev] 0.8.3 final

2003-09-08 Thread Martin Aliger
I tend to agree with you. Corporate users don't really gel with the opensource style 0.x release numbers. Lets table up a list of things to target at a 1.0 and see how that looks. Right :) As I'm corporate developer as well, I mostly agree with Sascha. 1/ 1.0 should contains VS.NET addin.

Re: [nant-dev] 0.83-rc3

2003-09-05 Thread Martin Aliger
Martin Aliger can probably wait for 0.8.4. Gert Driesen wrote: That is the intention yes, we could ofcourse skip the 0.8.3 release and start the 0.8.4 beta cycle ... I agree that having a 0.8.3 release with serious known issues might now be a good idea after all. Gert

[nant-dev] branching in nant

2003-09-04 Thread Martin Aliger
Hi all, I want to check whether directory exists and branch by the result. Is it possible in current NAnt? I add some if attributes for now but maybe this could be solved in general way. Maybe to set some ${result} property in tasks (as mkdir task in this case). It could be possible check that

[nant-dev] solution task question

2003-09-02 Thread Martin Aliger
Hi all, What should this code in Reference::GetReferenceFiles do? // Get a list of the references in the output directory foreach (string referenceFile in Directory.GetFiles(fi.DirectoryName, "*.dll")) { // Now for each reference, get the related files (.xml, .pdf, etc...) string

Re: [nant-dev] solution task question

2003-09-02 Thread Martin Aliger
- Original Message - From: Eddie Tse [EMAIL PROTECTED] To: 'Tom Cabanski' [EMAIL PROTECTED]; 'Martin Aliger' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, September 02, 2003 2:28 PM Subject: RE: [nant-dev] solution task question I noticed this today as well with the solution task

Re: [nant-dev] solution task assemblyfolders

2003-09-02 Thread Martin Aliger
Message - From: Jaroslaw Kowalski [EMAIL PROTECTED] To: Martin Aliger [EMAIL PROTECTED]; ! nant [EMAIL PROTECTED] Sent: Monday, September 01, 2003 5:48 PM Subject: Re: [nant-dev] solution task assemblyfolders Hi all! That's a very good idea, however just by looking at your patch I see few

[nant-dev] solution task assemblyfolders

2003-09-01 Thread Martin Aliger
Hi all! I implement that assemblyfolder subtag for solution as we discused it here. I hope my coding convention is ok (try to be close to yours). I'm also totally confused by security checks. Have you any experience with enabling read from registry? [it is ok for me without it, but...] There

Re: [nant-dev] last suggestion - Solution task again

2003-09-01 Thread Martin Aliger
? Also I'm not quite sure about naming. is assembly-folders proper name for that tag? And how to internally implement it? As list of paths? Fileset is not appropriate here. Maybe I could handle it simmilary as arg in csc? (only list tag I'm aware of) Martin Martin Aliger wrote: I did some

Re: [nant-dev] last suggestion - Solution task again

2003-08-29 Thread Martin Aliger
. Matt. Martin Aliger wrote: Odd... We simply check in .csproj files and leave .csproj.user files on each machine individually. We haven't had any issues with this. Are you perhaps talking about 3rd party references? Or GAC references? no - normal references to assemblies

Re: [nant-dev] last suggestion - Solution task again

2003-08-27 Thread Martin Aliger
Odd... We simply check in .csproj files and leave .csproj.user files on each machine individually. We haven't had any issues with this. Are you perhaps talking about 3rd party references? Or GAC references? no - normal references to assemblies. Unfortunattely we do not use CVS or similar

[nant-dev] solution task

2003-08-27 Thread Martin Aliger
. Martin Aliger gordic.gif

[nant-dev] solutiontask outputdir attribute

2003-08-27 Thread Martin Aliger
; } _settings.Add(@/doc: + _docFilename + @); Directory.CreateDirectory(Path.GetDirectoryName(_docFilename)); S pozdravem Ing. Martin Aliger gordic.gif

[nant-dev] OT: anonymous cvs

2003-08-27 Thread Martin Aliger
Why is anonymous cvs older than night build? I played quite long with cvs to get it work through our firewall to only get older files! I am annoyed. S pozdravem Ing. Martin Aliger gordic.gif

Re: [nant-dev] last suggestion - Solution task again

2003-08-26 Thread Martin Aliger
I'd recommend against comparing only filenames. This will likely end up causing trouble down the line. VS.NET is certainly a mess when it comes to hint paths, but I've found that they are generally accurate. I don't even think it uses them half of the time. :) Can you describe your

[nant-dev] Fw: two more problems in Solution task (path related)

2003-08-26 Thread Martin Aliger
Hi again, I found two more thinks: 1/ csc @temp-path\commands.txt do not start propertly, when temp-path is in x:\documents and settings becouse of spaces in path 2/ when extra output files are copied and source and dest is in same path - source is deleted! (I change smthing in /doc stuff, but

[nant-dev] patch suggestion - Resgen task

2003-08-22 Thread Martin Aliger
Hi all, I was quite long away, but now again working with NANT. I need some changes, so there is what I suggest. I will try get smaller blocks to be easy. First RESGEN. It writes some annoying messages even when verbose=false. It goes to ExternalProgramBase.cs: ---

[nant-dev] last suggestion - Solution task again

2003-08-22 Thread Martin Aliger
Last one - and I'm not sure there. There are problems with references between projects when projects have different output paths. Project references are ok, but external refenreces sometimes brokes. Currently nant compares files as full pathnames using path from HintPath attribute. I suggest

[nant-dev] suggestion - Solution task

2003-08-22 Thread Martin Aliger
Hi, I suggest to override OutputPath in .csproj in build-file. It could be useful to write some easy to maintain build files as that: target name=build solution configuration=Release output=${build.dir} projects includes

[nant-dev] RecompileNeeded enhancement

2002-10-08 Thread Martin Aliger
Hi all, I draft one enhancenment to recompile-needed feature in CompilerBase. I'm heading to compile mono classes by nant. This is lot of subprojects/namespaces and files and this feature is desirable. 1/ Added support for changed .build projects 2/ Bugfix/enhance subprojects recompilation

Re: [nant-dev] RecompileNeeded enhancement

2002-10-08 Thread Martin Aliger
That is why the command line used to compile the assembly should be saved and checked. If you changed the build file and it causes a command line setting to be changed the build will get executed. This gives you exactly what you are getting by depending on the build file except that if you

[nant-dev] Re: Fileset change

2002-09-30 Thread Martin Aliger
Hi, I just done somethink very simillar as addition to nant for mono. Mono classes build uses file called list which is in each directory of tree along with .build file (it is intended to run as mcs @list). So reference the same file within .build file seems logical. In this file are only

<    1   2   3