If this is a managed application you have to have the assemblies within the
same folder, in the global assembly cache, or a config file for the
application that specifies a path that is different from the 1st two
options I mentioned.

Thanks!  Robert Gruen - http://blogs.msdn.com/robgruen
Microsoft, VB.NET

This posting is provided "AS IS", with no warranties, and confers no rights.
--------------------
#Content-Class: urn:content-classes:message
#From: "GurriBurri" <gustavmango@hotmail.com>
#Sender: "GurriBurri" <gustavmango@hotmail.com>
#Subject: Assembly Reference
#Date: Thu, 27 May 2004 02:39:33 -0700
#Lines: 11
#Message-ID: <1357801c443ce$8436bbc0$a501280a@phx.gbl>
#MIME-Version: 1.0
#Content-Type: text/plain;
#    charset="iso-8859-1"
#Content-Transfer-Encoding: 7bit
#X-Newsreader: Microsoft CDO for Windows 2000
#X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
#Thread-Index: AcRDzoQ208r725sGQfWdwbcmY4ChYQ==
#Newsgroups: microsoft.public.dotnet.framework.clr
#Path: cpmsftngxa10.phx.gbl
#Xref: cpmsftngxa10.phx.gbl microsoft.public.dotnet.framework.clr:10711
#NNTP-Posting-Host: tk2msftngxa13.phx.gbl 10.40.1.165
#X-Tomcat-NG: microsoft.public.dotnet.framework.clr
#
#Hi there
#I have a peculiar prob. I am trying to build a file with
#testcases for NUnit in which I want to reference the
#Assembly with the code to be tested. The source compiles
#but when I try to execute the file in the NUnit console
#it doesn't find the Assembly. But if I copy the .dll to
#the working directory it works.
#I have tried to change the LIB env variable, set an /lib
#reference during compile time, but nothing works?
#
#
#

Right. This is why when you reference an assembly and build with Visual
Studio, it copies the assemblies that you referenced into your working
directory. That's how it works. :)

The LIB environment variable is used by the C++ compiler to locate .LIB
files during link time. It has no effect on runtime dependencies.