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?
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?