Re: [nant-dev] Solved: ReflectionTypeLoadException when using custom task

2004-03-22 Thread Gert Driesen
Thanks for the feedback, let us know if you come across any issues. Gert - Original Message - From: Garrett Smith To: [EMAIL PROTECTED] Sent: Sunday, March 21, 2004 12:58 AM Subject: [nant-dev] Solved: ReflectionTypeLoadException when using custom task I

[nant-dev] Possible reference problem

2004-03-22 Thread Nicklas Norling
Title: Possible reference problem Hi all. Since 0.84 is so stabile and nice I haven't really take my time to try out all the new good work for the solution task, until today. I must say it's a very impressive work. The solution task is now FAST. A lot faster then the old was. Howevery,

[nant-dev] cvs.exe - bad naming

2004-03-22 Thread Simon Steele
Hi, Can I suggest that cvs.exe (from sharpziplib) is called something else? We have lots of scripts that call out to cvs.exe. Now that there is one in the nant directory that gets executed instead of the one in the path. Unfortunately the sharpziplib one crashes quite a lot and doesn't provide

[nant-dev] VC++ Solution Build - bad build directory

2004-03-22 Thread Simon Steele
Hi, I've just tried the latest nightly build for building c++ projects in solutions - it's much better! Thanks! I'm still not quite there for my whole solution though. The solution I'm building has a Managed C++ project which is then used from C# projects. The mc++ project now builds correctly

Re: [nant-dev] cvs.exe - bad naming

2004-03-22 Thread Gert Driesen
I agree, perhaps we could not ship the cvs.exe executable at all as part of NAnt, but just direct users to the #cvslib website. Clayton, what do you think ? Gert - Original Message - From: Simon Steele [EMAIL PROTECTED] To: Nantdev [EMAIL PROTECTED] Sent: Monday, March 22, 2004 5:43 PM

RE: [nant-dev] cvs.exe - bad naming

2004-03-22 Thread Clayton Harbour
Hi Gert and Simon, I would prefer to just change the name of the sharpcvslib binary and leave it in the NAnt repository as it means the basic cvs commands work out of the box in a situation where there isn't a cvs binary installed (i.e. on a build server). It also makes it easier for me to keep

Re: [nant-dev] cvs.exe - bad naming

2004-03-22 Thread Scott Hernandez
Why do we need the managed executable (?) and the managed dll? If this is a win32 only binary, I would rather not see it in our dist. - Original Message - From: Clayton Harbour [EMAIL PROTECTED] To: Gert Driesen [EMAIL PROTECTED]; Simon Steele [EMAIL PROTECTED]; Nantdev [EMAIL PROTECTED]

RE: [nant-dev] cvs.exe - bad naming

2004-03-22 Thread Clayton Harbour
It is not a win32 only binary Scott, it is a command line client for sharpcvslib which is pure c#. Clayton -Original Message- From: Scott Hernandez [mailto:[EMAIL PROTECTED] Sent: March 22, 2004 7:43 PM To: Nantdev Subject: Re: [nant-dev] cvs.exe - bad naming Why do we need

Re: [nant-dev] Mail Task

2004-03-22 Thread Gert Driesen
Eric, Attachments should be specified as a fileset (see http://nant.sourceforge.net/nightly/help/tasks/mail.html). This was changed quite a while ago. Use this instead : mail from=[EMAIL PROTECTED] tolist=[EMAIL PROTECTED] subject=Daily Build for ${curDate} at ${curTime} was

Re: [nant-dev] cvs.exe - bad naming

2004-03-22 Thread Gert Driesen
Perhaps, you could remove the library too, and always have the cvs tasks wrap the commandline cvs client ? - Original Message - From: Clayton Harbour [EMAIL PROTECTED] To: Gert Driesen [EMAIL PROTECTED]; Simon Steele [EMAIL PROTECTED]; Nantdev [EMAIL PROTECTED] Sent: Tuesday, March 23,

RE: [nant-dev] cvs.exe - bad naming

2004-03-22 Thread Clayton Harbour
Actually there are a couple of tasks that I would like to add that are going to be a lot easier with the library so I would like to leave it (the tasks are cvslog: xml log report - useful for logging cvs activity, similar to ant log; cvslocalinfo: local cvs sandbox information - useful for