http://outerlevel.com/blog/2006/01/09/visual-studio-could-not-write-to-output-file/ Building a MicroISV Thu, 04 Feb 2010 16:16:05 -0500 http://wordpress.org/?v=2.9.1 hourly 1 http://outerlevel.com/blog/2006/01/09/visual-studio-could-not-write-to-output-file/comment-page-1/#comment-71 Jon Trainer Mon, 30 Jan 2006 13:33:28 +0000 http://www.outerlevel.com/blog/2006/01/09/visual-studio-could-not-write-to-output-file/#comment-71 Thanks Jason. I was not working in 'Release' mode so this would probably work. But, doesn't this strip the debug info that the debugger uses? I also have #if statements relying on the DEBUG value to be set for debugging code. These also would cease working. Thanks Jason. I was not working in ‘Release’ mode so this would probably work. But, doesn’t this strip the debug info that the debugger uses? I also have #if statements relying on the DEBUG value to be set for debugging code. These also would cease working.

]]> http://outerlevel.com/blog/2006/01/09/visual-studio-could-not-write-to-output-file/comment-page-1/#comment-70 jason Mon, 30 Jan 2006 06:24:58 +0000 http://www.outerlevel.com/blog/2006/01/09/visual-studio-could-not-write-to-output-file/#comment-70 An other work around is to switch to 'Release' configuration - wait while it does it's thing - delete the obj directory and then switch back to 'Debug'. This of course assumes you were working with Debug to begin with. This is slightly quicker than closing the process but equally as annoying ... An other work around is to switch to ‘Release’ configuration – wait while it does it’s thing – delete the obj directory and then switch back to ‘Debug’. This of course assumes you were working with Debug to begin with. This is slightly quicker than closing the process but equally as annoying …

]]>