Wilbert van Dolleweerd wrote:
actually it references the set of assemblies specified in {frameworkdir}/csc.rsp. You can have a look for yourself but here is a snippet:
<include name="Microsoft.VisualBasic.dll" /> <!-- third party assemblies --> <include name="eWorld.UI.DLL" /> <include name="FreeSMTP.Net.DLL" /> <include name="Microsoft.Web.UI.WebControls.dll" /> <include name="SU_WebControls.dll" /> <include name="richtextbox.dll" /> </references> <sources basedir="${VSS_WorkingFolder}">
<include name="**/*.vb" /> </sources> </vbc>
The VB.NET support in NAnt is better or worse than the support for C#. Only
the C# compiler itself is different : it references a set of system assembly
by default (in .NET 2.0 vbc will do this too),
------------------------------------------------------------
# This file contains command-line options that the C#
# command line compiler (CSC) will process as part
# of every compilation, unless the "/noconfig" option
# is specified.
# Reference the common Framework libraries /r:Accessibility.dll /r:Microsoft.Vsa.dll /r:System.Configuration.Install.dll /r:System.Data.dll /r:System.Design.dll ... ... ---------------------------------------------------------------
It would be quite simple to have the vbc task do somthing similar - ie read a list of references and namespace imports from a vbc.rsp file and pass them on to the the compiler. However if vbc.exe in .NET 2.0 will have this anyway it might not be worth it.
Ian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
