Scrub this - it was my mistake. Looks like I typo'd a source filename somehow and it
wasn't being thrown out. Is there a way of getting <csc> to throw an error in the case
when source files are missing, instead of just compiling the ones it does find and
carrying on as if nothing was wrong?
-----Original Message-----
From: Kenton Price
Sent: Wed 09/07/2003 10:51
To: [EMAIL PROTECTED]
Cc:
Subject: [Nant-users] Odd compilation problem using .NET Framework 1.0
Hi
I've got a prob with a DLL that NAnt 0.8.2 compiles on a machine that has .NET
Framework 1.0 on it, not 1.1. In short:
- it fails if I have a reference to the NAnt-compiled version of this DLL when
compiling another DLL
- it works if I have a reference to the VS.NET-compiled version of this DLL
when compiling another DLL
- it works if I have a reference to the csc-compiled version of this DLL when
compiling another DLL
so I think I've isolated NAnt as the problem. NAnt seems to compile the first
DLL without any problems - it's only when this compiled DLL is referenced by the
second DLL that it fails.
Here's my NAnt call to compile that first DLL, that fails when referenced by
the second DLL:
<csc verbose="true" target="library"
output="${build.dir}/bin/Resource.dll" debug="true">
<sources>
<includes name="AssemblyInfo.cs"/>
<includes name="IKey.cs"/>
<includes name="Key.cs"/>
<includes name="SessionKey.cs"/>
</sources>
<references basedir="${build.dir}/bin">
<includes name="System.dll" />
<includes name="System.Data.dll" />
<includes name="System.XML.dll" />
</references>
</csc>
Here's my working csc call that produces that same first DLL, and succeeds
when referenced by the second DLL:
csc /out:Resource.dll /target:library
/reference:System.dll,System.Data.dll,System.XML.dll assemblyinfo.cs ikey.cs key.cs
sessionkey.cs
Both nant and csc are called from a VS.NET command prompt that also has the
NAnt bin directory in its path.
In NAnt.exe.config I have <nantsettings defaultframework="net-1.0"> . I have
also commented out the supporting runtime - this makes the verbose <csc> call a lot
happier as it doesn't complain about missing framework 1.1 info:
<startup>
<supportedRuntime version="v1.0.3705" />
<!--supportedRuntime version="v1.1.4322" /-->
</startup>
I'm kinda stumped now. Any ideas? Have I missed something obvious?
Unfortunately I am unable to upgrade to the .NET Framework 1.1 in this project.
Many thanks if you can help.
Kenton Price
NHjyxu*jzí~}y~j
N�HS^�隊[)�{(��[���j� �J뢺k���y���Ʈ�����^�ا�j+x:0�Zu�ڕg�*)�jw`z֟�盢�0�
Z��(~�(���W���(}�i�֧�� �ɚ�X��X��֧�� ��b��,���y�+��m����+-��.�ǟ�� ���+-��b�ا~��j{n���
