>>There are ways of doing that - but it would be pointless. The DLL would not load unless it's dependent assemblies are present. > >Yes, it does not load but remains in the project directory. And, if I forget about it, when I build the Setup, it will be part of the Setup.exe. So, I need to think about excluding those files. That is why I thought there could be a way to do it.
But what I think Viv was getting at is that you still need to have it in your directory. I don't think the DLL that you *do* need will load if that other DLL is missing, even though you're not using it.
