Hello Arniec,

Did you check your installed settings? It sould accidently copy your dll.
Btw, how do u refer to that DLL?

---
WBR,
Michael  Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour 

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

A> I have created a shared assembly(adoio.dll)  I have set the parameter
A> to local copy = false,  but when I run my installer, I still get a
A> copy of this dll in my directory.  The intention was to have a single
A> copy in the GAC so if I wanted to update it, it would be done in a
A> single place.
A>
A> What am I missing?
A> Thank

I don't know what installer you're using, but in all setup projects I've
seen (including Visual Studio setup projects) the copy local in your compile
build has no effect on whether your assembly is installed into the GAC or
not. Are you adding project output/primary output to your application
folder? That will cause what you're seeing. Again, assuming VS setup
project, you need to do an Add Special Folder in your file system view,
choose GAC, add your assembly there, and put the other files in the
application folder, all this instead of using project output. This is all a
guess of course because you haven't decribed what you are doing in your
installer.

If you are doing ClickOnce deployment, make sure the BuildAction is also
"None". And look under ApplicationFiles and make sure it is marked as not to
be included.

RobinS.
GoldMail, Inc.
---------------------------------