Could not copy temporary files to the output directory

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Verane (verane.chanson_at_varianinc.com)
Date: 01/31/05 

Date: 31 Jan 2005 07:54:16 -0800

Hi,
I have read the thread named "Could not copy temporary files to the
output directory" on this newsgroup. And I have the same symptoms on
my machine. But I didn't find any solution suitable for me. (I don't
use ASP.NET or any web service at all, only windows forms).

Here is how I work :
I have a solution with 10 projects inside. Each of them is built in a
different directory (MyProject/bin/debug for each project). I have
then a post-build event that copy all those dlls in a single directory
called M:\bin.
(I have done that to avoid compiling all my projects in the same
directory, and because I need them to be in a unique directory to be
able to debug).
Each project has some references on assemblies that come either from
the same solution or from third party components. In each case I set
the reference by brwosing the dll in M:\bin and not using a 'project
reference'.
I always set 'local copy' to true.

the problem is that I randomly get errors that my dll could not been
copied in the output directory or I also get some 'post-build event
failed' when I do re-built.
I sometimes also get the same kind of errors about the .pdb files.

At the moment I do the rebuilt, my application is not runnig. Often I
have those problems just after having opened visual studio, even
before I have run my application once.

The only solution I have found for the moment is to close Visual
Studio, delete the .dll or .pdb and re open visual studio... This is
very annoying, because it takes a long time to open the solution...

Is there something I do wrong ?? Is there a workaround ??

Any help will be appreciated !
Thanks,
Verane.

Relevant Pages

  • Re: Dll download
    ... set the output directory for the DLL to be the source ... file directory of your Studio project, that way when it gets built, it ... replaces the one Studio is using. ... in Studio set the DLL ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Copying a DLL inside a solution
    ... I could hardly use post generation events for that, but it is not safe as ... I need to know exactly where the DLL application is for making the copy. ... project output directory, not to the remote D project output directory, ... Release in Release folder, both under the Solution directory, which should ...
    (microsoft.public.vc.ide_general)
  • Re: Copying a DLL inside a solution
    ... I could use macros like $, but $refers to the local E project output directory, not to the remote D project output directory, which is not guaranteed to always have the same name even for the corresponding configuration. ... This will cause the $to be the same for both E and D, and the Debug will be together in Debug folder, Release in Release folder, both under the Solution directory, which should be the parent folder of both of the project folders. ... but I'm afraid it would not give better results than the "post generation events" method that I quote: ... This is actually a problem that I recurrently get when building projects; the DLL project is not always written by myself, it is sometimes used by more than one solution, and the Debug or Release directories do not always have the same name as in the main project: they can sometimes be named Debug_Unicode, Debug_MBCS or something like this. ...
    (microsoft.public.vc.ide_general)
  • Re: Where are web app references stored?
    ... In website project of VS 2008, there are 4 types of references. ... Studio treats them differently and put them in different places. ... those project references will be stored in solution file. ... Whenever add an external DLL in VS 2008, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: I get some warnings that I dont understand when building the exe file
    ... Simply reference the dll's from where they are, ... my class libraries. ... The exe file are using six class library dll. ... When I use C++.NET the dll is always copied to the output directory even ...
    (microsoft.public.dotnet.languages.csharp)