NAnt - A .NET Build Tool

----- Original Message -----
From: "Giuseppe Greco" <giuseppe.greco@...>
To: "NAnt Users" <nant-users@...>
Sent: Monday, May 31, 2004 12:12 PM
Subject: [Nant-users] NAnt on Linux: gac


> Hi all,
>
> If I'm not wrong, the latest version of NAnt
> references the assemblies installed in the gac...
> but this is not always what one wants.

NAnt tries to resolve assemblies assemblies that cannot be located in the
current base directory, in the assembly directory of the current target
framework. It does not try to reference assemblies in the GAC.

>
> For example, I use assembler.exe/updater.exe to
> generate monodoc documentation, but at the moment
> these assemblies cannot be installed in the gac
> because the do not have a valid public key token.
>
> Furthermore, to have the <nunit2> task working
> correctly, one has to install the nunit.framework.dll
> assembly shipped with NAnt, but again, it cannot be
> installed in the gac because it has not a valid
> public key token...

The nunit.framework.dll that is shipped with NAnt doesn't have to be
installed in the GAC at all.  Ofcourse, you should make sure that you
reference the nunit.framework that is shipped with NAnt to build your test
assemblies, otherwise you won't be able to run your tests using the NAnt
<nunit2> task.

Mono currently ships with a beta version of NUnit 2.2.  Once this version is
released, we'll update NAnt to use this version too.

Gert

Yes, but "${framework::get-assembly-directory(target.framework)}"
returns /usr/local/lib/mono/1.0, which points to the GAC, and
to have the following task working, one has to install the
nunit.framework.dll assembly shipped with NAnt into the GAC:

<!-- global framework settings -->
<property
  name="target.framework"
  value="${framework::get-target-framework()}" />
<property
  name="assembly.dir"
  value="${framework::get-assembly-directory(target.framework)}" />
<property
  name="nunit.dir"
  value="${assembly.dir}"
  if="${platform::is-unix()}" />

...

<target
  name="test"
  depends="build"
  description="Tests the current configuration">
  <csc
    target="library"
    debug="${debug}"
    define="${platform::get-name()}"
    unsafe="true"
    output="${build.dir}/${package.name}/lib/${assembly}.Tests.dll">
    <sources
      basedir="${assembly}.Tests"
      failonempty="true">
      <include name="*.cs" />
    </sources>
    <references basedir="${build.dir}/${package.name}/lib">
      <include name="${assembly}.dll" />
      <include name="${nunit.dir}/nunit.framework.dll" />
    </references>
  </csc>
  <nunit2>
    ...
  </nunit2>
</target>

j3d.

On Mon, 2004-05-31 at 12:12, Giuseppe Greco wrote:
> Hi all,
> 
> If I'm not wrong, the latest version of NAnt
> references the assemblies installed in the gac...
> but this is not always what one wants.
> 
> For example, I use assembler.exe/updater.exe to
> generate monodoc documentation, but at the moment
> these assemblies cannot be installed in the gac
> because the do not have a valid public key token.
> 
> Furthermore, to have the <nunit2> task working
> correctly, one has to install the nunit.framework.dll
> assembly shipped with NAnt, but again, it cannot be
> installed in the gac because it has not a valid
> public key token...
> 
> May be I'm wrong... I'm just trying to understand
> the new layout.
> 
> j3d.
-- 
----------------------------------------
Giuseppe Greco

::agamura::

phone:  +41 91 604 67 65
mobile: +41 76 390 60 32
email:  giuseppe.greco@...
web:    http://www.agamura.com
----------------------------------------

Guis,
The nunit task should handle loading nunit.framework.dll from nants bin 
directory. If its not working for you there could be a linux specific 
issue. However copying nunit.framework.dll to

${build.dir}/${package.name}/lib/ should enable your tests to run fine without having to install it in the GAC.

Ian

Giuseppe Greco wrote:

>Yes, but "${framework::get-assembly-directory(target.framework)}"
>returns /usr/local/lib/mono/1.0, which points to the GAC, and
>to have the following task working, one has to install the
>nunit.framework.dll assembly shipped with NAnt into the GAC:
>
><!-- global framework settings -->
><property
>  name="target.framework"
>  value="${framework::get-target-framework()}" />
><property
>  name="assembly.dir"
>  value="${framework::get-assembly-directory(target.framework)}" />
><property
>  name="nunit.dir"
>  value="${assembly.dir}"
>  if="${platform::is-unix()}" />
>
>...
>
><target
>  name="test"
>  depends="build"
>  description="Tests the current configuration">
>  <csc
>    target="library"
>    debug="${debug}"
>    define="${platform::get-name()}"
>    unsafe="true"
>    output="${build.dir}/${package.name}/lib/${assembly}.Tests.dll">
>    <sources
>      basedir="${assembly}.Tests"
>      failonempty="true">
>      <include name="*.cs" />
>    </sources>
>    <references basedir="${build.dir}/${package.name}/lib">
>      <include name="${assembly}.dll" />
>      <include name="${nunit.dir}/nunit.framework.dll" />
>    </references>
>  </csc>
>  <nunit2>
>    ...
>  </nunit2>
></target>
>
>j3d.
>
>On Mon, 2004-05-31 at 12:12, Giuseppe Greco wrote:
>  
>
>>Hi all,
>>
>>If I'm not wrong, the latest version of NAnt
>>references the assemblies installed in the gac...
>>but this is not always what one wants.
>>
>>For example, I use assembler.exe/updater.exe to
>>generate monodoc documentation, but at the moment
>>these assemblies cannot be installed in the gac
>>because the do not have a valid public key token.
>>
>>Furthermore, to have the <nunit2> task working
>>correctly, one has to install the nunit.framework.dll
>>assembly shipped with NAnt, but again, it cannot be
>>installed in the gac because it has not a valid
>>public key token...
>>
>>May be I'm wrong... I'm just trying to understand
>>the new layout.
>>
>>j3d.
>>    
>>


-- 
Ian MacLean, Developer, 
ActiveState, a division of Sophos
http://www.ActiveState.com