"unexpected error creating debug information"

26 Comments

• Steven it's probably also the same problem I had few days ago. Check Index Server, and see if it's running.
  
  
  
  If you don't need it turn off the services, otherwise add some exclusion directories, the .Net temporary folders for a starter
  

• The problem can be caused by virtually anything which runs in the background and is triggered by file activity. Index server is one example, also anti-virus scanners tend to do the same.
  
  
  
  I get this occasionally in VB/C# but much more often with managed C++ projects. I'm not sure why...
  

• For the record, I am using VS.NET 2003. The one that keeps getting locked is a C# project (class library) in a solution with 4 other VB projects (3 class libs and a web). I'm wondering if the IDE real-time compiling of VB's IDE is hitting the PDF/DLL from the C# project and not cleaning them up.
  
  
  
  Using prcview, it's clear that only that one project's file are being referenced from the My Documents/Visual Studio Projects/ProjectName/obj/ folder. The rest (the other dlls and pdbs being locked/referenced by devenv.exe) are going to the shadow copy under Application Data/.
  
  
  
  Thanks for the link to Process Explorer - I'll check it out.
  
  

• I've made some good experience to switch from "Debug" to "Release" and back to solve this problem.
  
  But it isn't working all the time.
  
  

• Tried switching from Debug to Release, and it worked! Easier than shutting down, to be sure. Thanks for the tip, Denis!
  

• I've had this problem to, tis VERY annoying!
  

• Solution in this blog was extremely helpful to me as I've spent most of today trying to figure it out!!! Thanks guys!
  

• Good info. I have tried all of it and I still can't compile. Also, no one mentioned bind failures (FUSLOGVW.exe). I get these also. The ide is having trouble finding/loading the assembly.
  
  
  
  Any other help ??? Thanks!!
  

• Dont know if it really help but I heard about checking the option 'Launch folder windows in separate process' on Windows explorer
  

• Most likely, you have an ASPX file open in VS.NET that has embedded your control. The ASPX project opens the control DLL and keeps it open. If you just don't open the ASPX while in VS.NET, you will be able to compile your solution. Once you open it, you will likely have to restart VS.NET, since it obviously seems to cache these controls when rendering them in the WYSIWYG design-time viewer.
  

• If you run Build->Clean Solution this will take care of the issue as well.
  

• Hi buddy,
  Thanks a lot man. It helped me a lot and I have fixed the issue successfully.
  
  Thanks a lot once again.
  

• This post was very useful and informative. Thanks.
  

• delete only .pdb files about your project in obj and bin/debug folder and everything work fine..
  

• Thanks, fixed my issues!
  

• Thanks dude! Your solution works
  
  C-ya!
  

• Thanks, fixed my problem
  

• Yup it sure worked. Thanks much
  

• Awesome Post fixed my issue!
  I had to Kill a process from Task Management
  

• I had the same problema. Here the culprit was the Microsoft Live Sync which i used to use to make realtime backups of my source folders.
  
  Just disabled it and the problem is gone.
  

• you can make it through the rain. you stand up once again on my own.
  
  -----------------------------------
  

• many many thanx it goes great
  

• Rather beneficial posting Excited for additional content articles in your web-site.
  

• Thank u its working :) for me :)
  

• awesome! thanks a lot.
  

• Thanks for this, it was driving me nuts!