From: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
> Can you try the latest nightly build? Many, many <solution> bugs were
fixed
> since then.
I just tried nant-0.85-20040318.zip. No luck.
The good news is 1.) I've created a test solution and project that
demonstrates the problem. I have 2M zip file I can send along to
whomever wants it.
2.) I did a little debugging (BTW, I couldn't build nant w/VS) and found
the exception was thrown NAnt.VSNet.VcConfiguration.OutputPath.
The code assumes if GetToolSetting("VCLinkerTool", "OutputFile")
returns null, then GetToolSetting("VCLibrarianTool", "OutputFile");
must have something, and it returns that. In my case, neither
GetToolSetting()
calls return anything. This causes a crash further up. I have a test
version
of Nant where I cobble together an output path using the project name
(from Macros["ProjectName"]), which makes the problem go away, but
I'm not sure this is a good fix -- there are other places where
GetToolSetting("VCLinkerTool", "OutputFile") is called.
The problem project is a little odd. It has a modified Output Path property
of the Linker parameters -- since it wasn't shown in bold. But it looks
like the setting is back to what the default was. The .csproj file
certainly
shows no "OutputPath" setting for the VCLinkerTool.
Greg Arzoomanian
TailWind Solutions, Inc.
http://www.tailwindinc.com
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
