Two PACT compile errors

Last post 01-06-2006 2:27 PM by BenRosa. 2 replies.

Sort Posts:

  • Two PACT compile errors

    12-14-2004, 7:05 PM
    • Member
      35 point Member
    • joenace
    • Member since 12-10-2004, 11:27 AM
    • Posts 7
    Unable to write to output file 'C:\Documents and Settings\jnace\VSWebCache\JNACEXP\DotNetNuke\obj\Debug\DotNetNuke.dll': The process cannot access the file because it is being used by another process.

    Unable to write to output file 'C:\Documents and Settings\jnace\VSWebCache\JNACEXP\DotNetNuke\obj\Debug\DotNetNuke.pdb': Access is denied.



    Anybody know what is causing these errors. I used PACT to add a new module.


  • Re: Two PACT compile errors

    12-15-2004, 6:15 PM
    • Contributor
      2,484 point Contributor
    • toddhd
    • Member since 06-18-2002, 10:03 AM
    • Edina, MN
    • Posts 527
    This is a common error. One of two things will help. First, check your references. When you click on a reference and look at the properties, one property is called "Copy Local". It should be false for DotNetNuke, and most anything else. This usually fixes the problem.

    In order to be really safe however, just go into the Solution properties, then Configuration properties, and uncheck all the projects except your PA's. In other words, you don't need to recompile DNN and all it's projects every single time. This helped me a lot, and I never get that error now.
    -Todd Davis
    http://www.SeaburyDesign.com
  • Re: Two PACT compile errors

    01-06-2006, 2:27 PM
    • Member
      215 point Member
    • BenRosa
    • Member since 09-04-2005, 12:04 AM
    • Tampa, Florida, USA
    • Posts 43

    Todd:

    Yea, the reference that was giving me this problem was Microsoft.ApplicationBlocks.Data.  Upon changing Copy Local to "False" (in my local custom module solution) , those two error messages went away.

    Thanks...

    Ed

Page 1 of 1 (3 items)