[nant-dev] Specifing a Startup Object with VBC

2003-01-14 Thread Brant Carter
I found this msg in the archive with no answer: Hi I am busy compiling an exe and it requires a point of entry class (start up object), how do I declare this in the vbc target? Thanks Rosemarie Leighton (Financial IQ) The following works for me vbc target=winexe main=Form1 output=${output}

Re: [nant-dev] NUnit Error With NAnt...

2003-01-16 Thread Brant Carter
You might want to look at this article. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm l/cpconspecifyingassemblyslocation.asp I am pretty sure that the default is for it to look in the GAC and then to look in the current directory. You may have to specify your

Re: [nant-dev] Fileset references

2003-03-20 Thread Brant Carter
+1 for this. This would be really sweet. brant ... From: Philip Nelson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [nant-dev] Fileset references Date: Thu, 20 Mar 2003 11:15:20 -0800 (PST) So the two valid forms would be: 1.) (how things work now) foreach ... !-- stuff to do

[nant-dev] Solution Task Issues

2003-08-11 Thread Brant Carter
I am trying to get the solution task to work and found a couple of things that might make my (and others?) life easier. [1] When looking for references it uses the HintPath element on the project. Unfortunately this is not a reliable way to locate references. Visual Studio actual uses a

[nant-dev] NAntContrib Source

2003-08-14 Thread Brant Carter
Where can I get the NAntContrib source that is being use for the 0.83 release. I downloaded the source for NAnt and the binaries are in the \bin folder. The nightly builds for NAntContrib aren't correct. If someone has these files that would be appreciated. thanks brant

[nant-dev] Solution task Output Assemblies

2003-08-25 Thread Brant Carter
When compiling with devenv it will overrite the output assembly regardless of its file attributes (ie: ReadOnly). The solution task does not do this. Here is a patch to synch the two behaviours: NAnt.VSNet/Project.cs //THIS LINE MAKES THE OUTPUT FILE WRITTABLE System.IO.File.SetAttributes

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

2003-08-26 Thread Brant Carter
We solved this problem by creating a tool to update the .user files for each developer. It scans the directory tree and then creates a .user file for each .proj file with the correct reference path for that workstation. brant ... From: Martin Aliger [EMAIL PROTECTED] To: Matthew Mastracci

Re: [nant-dev] Licensing

2003-10-10 Thread Brant Carter
I think we should ask ourselves what types of uses we would want NAnt to be available to. Here are two scenarios. [1] A commerical company wants to release a custom task and charge money for it. Do we want to allow this? [2] A commerical company wants to distribute a customized version of

RE: [nant-dev] New to the list

2004-03-19 Thread Brant Carter
I was having this same problem! Thanks for the script. +1 for a ant task brant ... From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [nant-dev] New to the list Date: Fri, 19 Mar 2004 08:57:55 -0500 Hi everyone! I joined this list because there are some differences between Nant and

RE: [nant-dev] solution changes

2004-11-12 Thread Brant Carter
In the 0.84 build there is a bug (keep forgeting to get an official patch) where the solution task will fail if the output assembly is read-only on the drive. Normally you would think this is the desired behaviour but it is different that what VS.NET does. We actually rely on this bug to make