Re: 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: Yunus Emre ALPÖZEN (yemre_at_msakademik.net)
Date: 01/31/05 

Date: Mon, 31 Jan 2005 18:12:21 +0200

It is my nightmare. Today I got this error seven times... While closing
VS.NET it gives an error message and ask me to report this bug.... Restarts
VS.NET, and then everything works fine for a while... 

-- 
Thanks,
Yunus Emre ALPÖZEN
"Verane" <verane.chanson@varianinc.com> wrote in message 
news:5b21b1a9.0501310754.63a0d546@posting.google.com...
> 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: error in loading dll/missing Ref Edit Control
    ... I removed the personal.xls file altogether and I was able to start up Excel ... directory and once again I got an error message upon start up (and of course, ... I think I have to resolve this load dll issue ... Next Add the reference for the REFEDIT. ...
    (microsoft.public.excel.programming)
  • Re: fatal error CS0009: Metadata file
    ... I guess I'm still trying to figure out terminology so I'm don't know what a managed assembly is or what a com dll is. ... Anyway I still get the error message. ... >> Dave, ... then you will have to create an interop assembly and reference that. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Error while referencing my own assembly
    ... You get this error message for any dll added to the project which is not in ... the standard sdk folder (the default list in the Add Reference dialog. ... you know your dll is compiled for the compact framework you can ignore this ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Cant reference dll
    ... COBOL program that is 32 bit. ... The error message says "Please make sure the file is accessible and that it is a valid assembly or COM component. ... You can't add a reference to a DLL to your project unless it's an assembly or a COM library. ...
    (microsoft.public.dotnet.languages.csharp)
  • VB FAQs (Interview Questions) lot lot
    ... Consider two objects, A and B. A holds a reference to B, ... Why do so many example programs not use the DLL name ... Private Declare Function SendMessage Lib "user32" ... Private Const BUFFER_LENGTH As Long = 255 ...
    (microsoft.public.dotnet.languages.vb)