Guess I'll just talk to myself here. ;-)
I excluded the assemblies from the setup project dependency list so it would
create the package without them and it seems to work OK. I don't understand
why I needed to do this but it's not really a major thing. I just worry
that I had to do it because I did something wrong with my setup project.
On another note, I originally had my references pointing directly at the
DLL's but then strong named them and installed them to the GAC. When I went
through and recreated the references, they would show up correctly until I
did a build then the properties for the reference would revert back to the
original values. I ended up renaming the directory holding the original
libraries and finally got it to work after a little more tweaking. I
couldn't figure out where the old property values were being retrieved from
though. I looked at the .proj file and it had the correct values. Does
anyone know where else I shoudl have looked?
Thanks,
Chris
"Chris" <di*****@hotmail.com> wrote in message
news:jP********************@giganews.com...
Hi,
Is it normal for dependencies found by a setup project to be included in
the MSI even if they are references to DLL's in the GAC? I have several
references in a project that are to GAC resources but they are being
packaged up into my MSI. I thought if Copy Local was set to false, the
files would not be included. Is something not right or do I not
understand what is meant to happen here?
Thanks for any help.
-Chris
