Debugging assemblies: Forcing EXE to reload DLL

  • Thread starter Thread starter _D
  • Start date Start date
D

_D

When debugging an assembly, obviously a startup Exe file must be set.
I've run into a snag once in a while that appears to be caused by VS
referring to the Exe's *local* copy of the target DLL rather than the
one that has just been recompiled.

Is there an recommended method for ensuring that a newly compiled DLL
also gets copied over the DLL in the startup Exe's folder?
 
_D said:
When debugging an assembly, obviously a startup Exe file must be set.
I've run into a snag once in a while that appears to be caused by VS
referring to the Exe's *local* copy of the target DLL rather than the
one that has just been recompiled.

Is there an recommended method for ensuring that a newly compiled DLL
also gets copied over the DLL in the startup Exe's folder?
Click to expand...

Questions:
1. is the project for the dll in the same solution as the exe project?
2. if it is, did you add a reference to the project or to the dll?

If the answer to #1 is "yes" and to #2 is "to the dll", try adding a
reference to the project instead, this will ensure VS copies the fresh
dll to the output directory for the exe project.

Other than that I don't know why that should happen.
 
Back
Top