innovate
asked on
DLL's locked when compiling or executing in debug
We are developing a large application in C# with multiple projects. Recently one dev. PC has a problem compiling and claims certain project DLL's can't be overwritten as "they are in use by another process". There is no application executing and often after much messing around (deleting DLL's, compiling projects in order of dependancy etc) the exe. project can be compiled and run. The troublesome Dll's can't be manually deleted unless VS is closed and even if it is closed and they are deleted then they are locked next time you try and compile. It is very sporadic with sometimes only one Dll being a problem, sometimes more.
I've checked dependancies and all seems fine. After deleting local source files and then retrieving from SourceSafe it worked fine for a while but now is almost impossible to run again.
Using
DynaZip Max 5
SyncFusion
Framework SP1
COM interop with word and excel.
Although none of the other Workstations seem to have this problem.
Anyone had similar probs. and found a solution?
I've checked dependancies and all seems fine. After deleting local source files and then retrieving from SourceSafe it worked fine for a while but now is almost impossible to run again.
Using
DynaZip Max 5
SyncFusion
Framework SP1
COM interop with word and excel.
Although none of the other Workstations seem to have this problem.
Anyone had similar probs. and found a solution?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Neither answer was correct but both relevant to DotNet. The cause was the DevEnv having a bug that did not release the Dll's after stopping debugging. This problem does not seem to exist in VS 2003
ASKER