Error Creating Source Debugger Information
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about
Visual Studio Unexpected Error Creating Debug Information File Access Is Denied
Stack Overflow the company Business Learn more about hiring developers or posting ads tfs build csc unexpected error creating debug information file with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow could not write lines to file obj debug access to the path is denied is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Unexpected Error creating debug information file GG.PDB“--” up vote 22 down vote favorite
Unexpected Error Writing Debug Information The Method Or Operation Is Not Implemented
1 When I try to build my project, it returns the following error: Error 1 Unexpected error creating debug information file 'D:\Documents\Lance\Documents\School\Capstone\GG\GG\obj\Debug\GG.PDB' -- '' GG I've recently had the misfortune of having my PC restart on me, due to sudden power supply problems (maybe). This is while the project was building, before this problem started. When the PC came back online I've noticed that the changes I've made to the
Csc Fatal Error Cs0042
program prior to the sudden power down was not saved. And, it won't build anymore. c# .net visual-studio debugging share|improve this question edited Jul 31 '11 at 2:13 CharithJ 26.3k117393 asked Jul 31 '11 at 0:32 zack_falcon 99452657 4 Try cleaning the solution (under Build menu in VS) –Cameron Jul 31 '11 at 0:33 1 have you tried to do a clean build? –Daniel A. White Jul 31 '11 at 0:33 2 Are you using an version control system? May be any locking issue? –CharithJ Jul 31 '11 at 1:19 @ CharithJ, I'm not using any version control system (whatever that is, sorry, new guy). Just 'vanilla' Visual Studio 2005. @ Cameron, thanks! That worked. –zack_falcon Jul 31 '11 at 2:11 @Cameron, I forgot to ask all these years - I just noticed it because it got a Famous Question badge - and I do apologize sincerely, but could you put your comment as an answer, so I could accept it? –zack_falcon Feb 2 '15 at 14:35 | show 1 more comment 8 Answers 8 active oldest votes up vote 18 down vote accepted As requested, my comment as an answer: Try cleaning the solution (under the Build menu i
External This item may be valid but belongs to an external system out of the direct control of this product team. A more error cs0041: unexpected error writing debug information detailed explanation for the resolution of this particular item may have
Debug Being Used By Another Process Visual Studio
been provided in the comments section. 1 0 Sign into vote ID 813202 Comments 4 Status Closed Workarounds .pdb the process cannot access the file because it is being used by another process 0 Type Bug Repros 0 Opened 1/8/2014 1:07:48 AM Access Restriction Public Description ASP .NET Web site, using Visual Studio 2013 Express. DETAILS ATTACH A FILE EDIT THIS http://stackoverflow.com/questions/6886790/unexpected-error-creating-debug-information-file-gg-pdb ITEM Assign To Item can only be reassigned when it is active. Comments (4) | Workarounds (0) | Attachments (1) Sign in to post a comment. Please enter a comment. Submit Posted by Microsoft on 1/9/2014 at 10:39 PM Thanks for your feedback. I'm glad to hear that your issue has been resolved. Based on your description, I https://connect.microsoft.com/VisualStudio/feedback/details/813202/unexpected-error-creating-debug-information-file-c-app-code-pdb will close this issue. Should you find any bugs in the future, please feel free to let us know. Posted by Boris Gappov on 1/9/2014 at 8:38 AM I found the source of the problem and fix it. It was a optimizeCompilations="true" attribute in the web.config file in system.web -> compilation section. Thanks! Posted by Microsoft on 1/8/2014 at 7:14 PM Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.Could you please give us a demo project to demonstrate this issue so that we can conduct further research?Please submit this information to us within 4 business days. We look forward to hearing from you with this information. Microsoft Visual Studio Connect Support Team Posted by Microsoft on 1/8/2014 at 1:50 AM Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com) Sign in to post a workaround. Please enter a workaroun
dll(s) in the /obj/ folder of library components. The fix that I have at the moment is as follows: Shut down VS.NET Browse to the project in http://weblogs.asp.net/ssmith/23755 windows explorer Delete the /obj/ folder. Delete the project outputs (.dll and .pdb) from /bin (not sure this step is necessary) (can't hurt, might help) -- delete the project outputs from any other project /bin folders in the solution that is having issues. Restart VS.NET Rebuild Laugh the next time you hear that DLL Hell is no more in .NET... Update: Just unexpected error deleting /obj/ after closing VS.NET does it. Ambrose pointed me to prcview.exe and that demonstrated that it is in fact devenv.exe locking the file, so it's VS.NET's own fault, not Index Server or anything else that is to blame. Listening to: Disturbed - Remember 26 Comments Steven it's probably also the same problem I had few days ago. Check Index Server, and see unexpected error creating 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 Paschall - Tuesday, August 12, 2003 2:36:00 PM 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... Addy Santo - Tuesday, August 12, 2003 3:09:00 PM 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 c