csc unexpected error creating debug information file access is denied
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings unexpected error creating debug information file the process cannot access the file and policies of this site About Us Learn more about Stack Overflow unexpected error creating debug information file c# the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation visual studio unexpected error creating debug information file Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them;
Fatal Error Cs0042: Unexpected Error Creating Debug Information Fileit only takes a minute: Sign up Unexpected Error creating debug information file GG.PDB“--” up vote 22 down vote favorite 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 could not write lines to file obj debug access to the path is denied 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 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.2k117393 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 bad
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 Stack Overflow the tfs build csc unexpected error creating debug information file company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions
Unexpected Error Writing Debug Information The Method Or Operation Is Not ImplementedJobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million
Csc Fatal Error Cs0042programmers, just like you, helping each other. Join them; it only takes a minute: Sign up TFS: cannot build my app, CS0042: Unexpected error creating debug information file. Access is denied. up vote 5 down vote http://stackoverflow.com/questions/6886790/unexpected-error-creating-debug-information-file-gg-pdb favorite I am trying to deploy my MVC app, but in the TFS build I get this error message; CSC : fatal error CS0042: Unexpected error creating debug information file 'c:\Builds\2\STAS\STAS\Sources\Documents and Settings\jyothisrinivasa\My Documents\Visual Studio 2010\Projects\STAS\STAS\obj\Debug\STAS.PDB' -- 'c:\Builds\2\STAS\STAS\Sources\Documents and Settings\jyothisrinivasa\My Documents\Visual Studio 2010\Projects\STAS\STAS\obj\Debug\STAS.pdb: Access is denied. I have excluded the Debug directory from my application, so why am I getting this? tfs share|improve this question asked Dec 14 '11 at 17:08 Jyothi Srinivasa 2942718 http://stackoverflow.com/questions/8508641/tfs-cannot-build-my-app-cs0042-unexpected-error-creating-debug-information-fi It's possible you have a read-only version already in that location. Have you looked? –Nick Nieslanik Dec 14 '11 at 22:10 1 There is something going on with this. CSC creates pdb files. If the build completes successfully, they are left writable. But in some cases, probably build failures, they are left read-only. This causes future builds to fail b/c a read-only file exists at the target path. I think it's a bug of sorts because it renders the build process not ACID (because it's not isolated b/c it's not repeatable), but I can't narrow in on the problem further just yet. Extra lines of code would have to be added to the build to first clean up a possible previous failed run. –toddmo Feb 18 '13 at 19:32 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote Delete the obj folder! It should work. share|improve this answer answered Jan 25 '15 at 4:33 Ayyappan 111 The obj folder seems to be included in TFS –Ayyappan Jan 25 '15 at 4:34 add a comment| up vote -1 down vote It is probably still checked into TFS. share|improve this answer answered Mar 19 '12 at 23:26 Darek 2,9811129 add a comment| Your Answer draft saved draft discarded Sign
is being used by another process. – compiler error? How do I – Solve the – Unexpected error creating debug information file .pdb. The process cannot access the file because it is being http://crayveon.com/solve-unexpected-error-creating-debug-information-file-pdb-process-access-file-used-another-process-compiler-error/ used by another process. – compiler error? Written by Cornelius J. van Dyk on May 4, 2010. Posted in How Do I... As a SharePoint Developer, you may run across this error at some point. It is most common when you’re trying to recompile a SharePoint binary, from aVisual Studiosession ON the actual SharePoint server. Of course, in most normal unexpected error situations, it’s unthinkable to run the compiler on the server, but as SharePoint developers, we know there is no other way to code for the platform so it’s pretty muchSOPfor us. The problem lies in the locks that are taken by the compiler process on the debug info file. Often the locks are taken by your last debug session and unfortunately unexpected error creating the locks aren’t always released, even though you’re the same user from the same application. Call it a multi threading anomaly or something. Whatever it is, this happens in Visual Studio 2008. EnterProcess Explorer! This little gem byMark RussinovichfromSysInternals, has been around for a long time, now in it’s12th version. Microsoft bought SysInternals a couple of years ago, and with it, Mark’s great mind. I must say, it was probably one of the smartest acquisitions thatRedmondhas ever made. But I digress. So, if you have Process Explorer installed (if you don’t,download it nowand do so), it generally lives in the C:\Program Files\Process Explorer folder. To unlock your files and resume your compilation, follow these easy steps: Open Windows Explorer. Browse to the C:\Program Files\Process Explorer location, or any other alternative location where you may have installed Process Explorer to. Double click “Procexp.exe” to launch Process Explorer. Once Process Explorer opens, it will display a list of all active processes on your system. Odds are that your .pdb file is NOT shown here. In the top menu, click the “Find” menu item.