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 vbc is called, the temp file has only been partially written (it's failing on a clipped path partway through the file).
So if my temp file should read something like:
/debug
"/define:DEBUG=True"
"/define:TRACE=True"
"/imports:Microsoft.VisualBasic,System,System.Collections,System.Data,System.Diagnostics"
"/rootnamespace:SPIRIT.ExperimentTrial "
/nologo
"/target:library"
"/out:D:\Data\Projects\Product Development\SAFE\debug\SPIRIT.ExperimentTrial.dll"
"/reference: [1 line per ref here]"
"/resource: [1 line per resource here]"
"/define:DEBUG=True"
"/define:TRACE=True"
"/imports:Microsoft.VisualBasic,System,System.Collections,System.Data,System.Diagnostics"
"/rootnamespace:SPIRIT.ExperimentTrial "
/nologo
"/target:library"
"/out:D:\Data\Projects\Product Development\SAFE\debug\SPIRIT.ExperimentTrial.dll"
"/reference: [1 line per ref here]"
"/resource: [1 line per resource here]"
"D:\ [path to a source file here]"
It gets clipped somewhere in the source file section - and the clip usually causes an incomplete path, resulting in a VBC exception:
[vbc] vbc : Command line error BC2001 : file 'D:\Data\Projects\Product Development\SAFE\Source Code\SPIRIT\Components\ExperimentTrial\UI\Actio' could not be found
The current workaround I'm using is to temporarily map a drive deeper in the source tree for the purposes of building this one assembly. (to shorten the paths, causing a smaller temp file to be written).
I can send the verbose output (but it's apparently to large to submit to the user list). I can't include the sources.
Running on Windows 2000
Targeting framework 1.0a
Intel Pentium 1600
500 meg RAM
Regards,
-Josh
