devenv.exe is fondling my dlls[Answered] RSS

• • Reply
  jugisahunk

  None

  0 Points

  11 Posts

  devenv.exe is fondling my dlls

  Nov 26, 2007 12:24 PM|jugisahunk|LINK

  I have a master solution containing 10 projects; two of those projects are web applications and the rest are class libraries.  Both Web applications depend on the same project.  When I make changes to that dependency and "play" or debug the startup web application, I get an error stating:

  •  Cannot copy assembly 'AssemblyName' to file 'C:\WorkingDirectory\SolutionName\WWWRoot\WebAppName\bin\AssemblyName.dll'.  The process cannot access the file because it is being used by another process.

   Using ProcExp.exe, I see that devenv.exe has a handle on AssemblyName.dll.  Does anyone know what's going on, or if there is a work around?
   

• • Reply
  Benson Yu -...

  All-Star

  30432 Points

  2481 Posts

  Re: devenv.exe is fondling my dlls

  Nov 28, 2007 10:23 PM|Benson Yu - MSFT|LINK

  Hi jugisahunk,

  Based on my research, I suggest you to try one of the following workarounds:

      * open project properties and edit pre-build events:

  if exist "$(TargetPath).locked" del "$(TargetPath).locked"
  if not exist "$(TargetPath).locked" move "$(TargetPath)" "$(TargetPath).locked"

      * If the control library project contains resx files, add the following property to the first <PropertyGroup> in the project file:

  <GenerateResourceNeverLockTypeAssemblies>true</GenerateResourceNeverLockTypeAssemblies>

  For more information, please refer to the link below:

  http://connect.microsoft.com/VisualStudio/feedback/Workaround.aspx?FeedbackID=114694
  

  Sincerely,
  Benson Yu
  Microsoft Online Community Support
  
  Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.
• • Reply
  jugisahunk

  None

  0 Points

  11 Posts

  Re: devenv.exe is fondling my dlls

  Nov 29, 2007 10:09 AM|jugisahunk|LINK

   Thanks Benson,

   This appears to exactly address my problem.  It definitely has the feel of a bug, thus I was not surprised to read in the article you linked to that it is indeed a bug.  Thanks for your help.