What exactly is the difference here? The reason I ask is I wonder if one will go out and recopy the dll's from their source directories replacing the local copies in the project bin directory.
Printable View
What exactly is the difference here? The reason I ask is I wonder if one will go out and recopy the dll's from their source directories replacing the local copies in the project bin directory.
Heres a quick answer I found on the web
Quote:
Rebuild performs an extra "clean" operation step, cleaning all intermediary
files and output directories before building the solution.
If you use the command line /rebuild is equivalent to /clean /build
Well,hmm, here's my situation:
I have 3 projects in my solution. The main project (startup) is a Windows Application, and one is a class library project.
The IDE, by default, will make a copy of the class library dll, and stick it in the Windows Application bin directory when you set a reference to the class library from the Windows App project.
So anytime I make changes to my class library, I have to unset the reference to it in my Windows Application, and reset it, so the IDE will go fetch the dll from the class libary bin folder.
I saw a property on the references that you can switch from Copy Local = true, or false. It's on True by default.
I had thought if I changed it to false, the Windows Application will always use the source copy (not a local copy) when building, but then I get a 'cannot copy reference to output directory error'.
How to solve this?
In your references, if you reference the project for the dll instead of the dll itself it will automatically update for you. This assumes that the dll project is one of the projects in the solution.
Thanks Ednesis, you know I never even noticed the Projects tab when you're adding a reference. Phew. That should be a tip of the day.
I believe you can also just click on the reference to select it and then click the refresh icon that appears at the top of the soultion explorer.
Yes, the refresh works for me too