I have an assembly that is currently built from ~300 source files.
The solution is huge, and the source tree is deep - causing the source paths to be abnormally long.
It looks like nAnt is writing the vbc params to a temp file (which is good) but vbc fails in this case (which is bad).
It appear
I have an assembly that is currently built from ~300 source files.
The solution is huge, and the source tree is deep - causing the source paths to be abnormally long.
It looks like nAnt is writing the vbc params to the temp file (which is good) but vbc fails (which is bad).
It appears that when
On Wed, 23 Feb 2005 10:21:59 -0800, Jeff Rodenburg
<[EMAIL PROTECTED]> wrote:
> My questions:
> - Do I require the individual .csproj files to be current for a NAnt
> build script? Do I have other options to use besides those files?
The csc task can build source files based on patterns, lists,
wha
What I do is something like this:
where I am explicitly setting the framework version to build with like this:
The trick then is other references (as merging filesets is not
currently trivial). I use a property to identify the ref path:
To get the tab to display I had to:
install nantrunner
start VS.NET 2003
remove the .build file from a project
remove nantrunner from the active addins list
add nantrunner to the active addins list
add the previously removed build file
However, after adding the .build file I get the following exc
Using 0.85-rc1 binaries, .NET 1.0a Framework, win2K
The workaround I am using is to quote the path:
Came across this yesterday, thought I'd post it though it certainly
doesn't appear urgent.
-josh
---
The SF.Net email is sponsored by: Beat