Visual Studio Debugger General FAQ

Question

I am excited to announce the availability of the following FAQ paper which lists some of the questions frequently asked by the Visual Studio Debugger forum members. This paper has covered many parts of Visual Studio Debugger from source/symbol server to asp debugging to stored procedure debugging, remote debugging, etc . Although it’s far from complete, but this is the first attempt our forum support team has been trying to make to help development community members find the answers to their questions much easier and fast, and it’s always the top priority for our team to make the MSDN forum a good place for developers to ask questions, talk about technologies etc. With time goes on, this thread will be enhanced with more FAQs and content, so we really welcome and appreciate any feedback or suggestion on how to improve it.

 

Contents

 

1.      How do I configure Visual Studio to debug .NET Framework source code?

2.      How do I configure Visual Studio to use Microsoft Symbol Server?

3.      What’s the difference of pdb files from Microsoft Symbol Server and Microsoft Reference Source Server?

4.      How do I debug classic ASP application in Visual Studio 2005/2008?

5.      How do I enable script debugging for classic ASP applications in IIS6?

6.      How do I debug stored procedure using Visual Studio 2008?

7.      How do I implement remote debugging with Visual Studio 2008?

8.      How do I implement a custom debug visualizer?

9.      How do I disable auto JavaScript code debugging with Visual Studio 2008?

10.  How do I troubleshoot “symbol file could not be found” issue?

11.  How do I troubleshoot “the breakpoint was not hit” issue?

 

 

Answer 1

Great thanks.

Now please can you add number 12, How to stop the error

Error 1 Unable to copy file "obj\Debug\mysoft.exe" to "bin\Debug\mysoft.exe". The process cannot access the file 'bin\Debug\mysoft.exe' because it is being used by another process.

it is costing me so much time....

Answer 2

I occasionally see the same problem after my application has crashed. In my case it's because my app is still running somewhere, even though I can't see it. Go to the Task Manager Processes list and kill it if it's still there.