CopyLocal is just a visual studio directive. It tells it whether or not to
copy the file to the build directory or not.
It is not in any way related to wheret he file has to be located at run
time. And the project file is again, just something for visual studio to
help it keep track of what is in your project, etc.
All of this, is just to help visual studio properly build your project.
At run time, the file has to be either wherever the executable is, or in the
GAC. There are ways to set up config file settings to tell the executable
to look in a subdirectory as well.
"Toma Marinov" <To*********@discussions.microsoft.com> wrote in message
news:C4**********************************@microsof t.com...
Hello !
I have a client Win application on VB (2005). I want to use my DLL which
is
on a server and I made a Reference to this DLL. But I dont want this dll
to
be copied localy and set property CopyLocal to False. When I execute the
application I recieve an error message that file couldnt be found /because
it
is searched localy/
I check my Reference paths in Project properties - there is a valid path
to
the dll on the server
I dont use GAC ..
So, can I reference a DLL from a server with CopyLocal = false and without
GAC ?
Kind regards,
Toma