Automatically Copy Dependancies?

[Denaes]

The program I'm using uses the Flexgrid from C1 and two of my own personal controls.

 

When I add my own two controls to the project, their respective .dll is copied to the bin directory.

 

The c1 (which I take it, is registered with .Net) was not automatically copied.

 

The program works fine in the IDE, but when I emailed it to a collegue, it gave .dll errors. I assumed the relevent .dll data was written into the binary exe for the project, because their .dll's arn't in the directory.

 

It turns out that the project will run anywere on my machine becuase the c1 dll's are registered, but when he tried to run it, it would ask for specific .dll's.

 

We had to exchange like 5 emails with me emailing him the dll's it was asking for (because it won't ask for the other 5 until it gets the first).

 

This is a bit silly.

 

The Bin directory is the output directory and should contain all that is needed to run the app short of the .Net framework.

 

Is there an option I'm missing that would copy the dll's over automatically? Or do I have to open up the References and try to hunt everything down by searching on my computer?

 

Currently I don't have a 2nd PC to run these sorts of compatability tests on, and the .Net framework hasn't been ported over to OS X yet, so my other machine is of no help.

[Nerseus]

References will be copied to the bin\Debug or bin\Release folder only when "Copy Local" is set to true. This defaults to "False" for references in the GAC (such as System, System.Windows, and probably Component1).

 

I think you can toggle the "Copy Local" to true for all your references (easy solution) or create a new Setup project and have it do the copying for you.

 

I don't know if the "Copy Local" will get you all the dependencies or not. References in the GAC register themselves and, in doing so, mark other DLLs as references. So System.Windows has System as a dependency (as a bad example). I'm not sure if setting "Copy Local" will copy ALL the dependent DLLs to the bind folder, so you still might have problems. You can try it, but if you run into problems it might be easier to just create the Setup project.

 

-Nerseus