By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,910 Members | 1,036 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,910 IT Pros & Developers. It's quick & easy.

Compilation : The process cannot access the file ...

P: n/a
> Xxxxx : error PRJ0008 : Could not delete file 'd:\xxxxxxx.dll'.
Make sure that the file is not open by another process and is not write-protected.
LINK : fatal error LNK1168: cannot open ../../Debug/xxxxx.dll for writing

The file 'xxxxxx.dll' cannot be copied to the run directory. The process cannot access the file because it is being used by another process.
Could not copy temporary files to the output directory.

I have a big problem. I've had it for a long time but it recently got bad to
the point I cannot function with it anymore. We have a rather big solution
(47 projects). About half these projects are plain C++ win32 projects (DLLs
which export classes/functions/data). Half of those left are COM objects
which wrap some of the C++ DLLs. The others are VB.NET interface projects
which use the COM objects. The main application (EXE) is VB.NET...

A couple of these COM wrappers AS well as some of the VB projects are
dependencies of several/most of the VB projects and almost everytime I
compile the whole solution (or parts of it for that matter) I will get one
or more of the errors listed at the beginning of this msg. The usual fix is
to flush all debug data, close VS, reboot machine and then recompile all and
I'm ok for a couple more hours... Now it's got to the point i have to reboot
of EACH compilation....

ALL output of these projects is directed to the same directory (for
debugging and deployment reasons, mainly -- they are all inter-dependant)
and from what I could find this is part of the problem. We're still using
v1.0 of .NET and I suppose this could also be part of the problem. I'll
continue reading documentation to try and understand but I guess experience
from other programmers who've undoutbly hit the same problem would probably
be more interesting..........

Anyone can give me a hint on how to make all this work without resorting to
a batch file to copy all files to the EXE's debug directory or other ugly
tricks of the like?

Thanks in advance!

Nov 20 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.