| Thread | Last Post | Replies |
|
| debugging a third party component | 30 Jul 2009 05:30 GMT | 11 |
I guess I did not do the right thing. Somehow I cannot debug our third party's component. We have a component developed by our vendor. Both dll and pdb were provided. So I think I can debug this component if I want to.
|
| Debug.WriteLineIf -- Compile Error in Realse Version | 14 Jul 2009 21:09 GMT | 3 |
Visual Studio 2005 SP1 VB.NET I have the following construct: #If DEBUG Then Dim bDebug As Boolean = True
|
| breakpoint was set to the same file name in different directory | 12 Jul 2009 20:49 GMT | 8 |
I am using vs2005. I also have vs 2003 installed on my computer(XP pro) When I tried to insert a breakpoint by clicking on the left side of a line in the file named default.aspx.cs in a directory, GS, it automatically jumps to the same file named
|
| Disable first-chance exception only in specific function | 08 Jul 2009 10:03 GMT | 3 |
Good Morning, Is it possible to disable first-chance exception handling within a specific function only? I need to see first-chance-exceptions for that exception in other functions
|
| How to determine line causing error | 02 Jul 2009 16:27 GMT | 5 |
Still migrating and recoding apps from vb6 to vs 2008. Can't see the easy answer to this one. Anyone able to help? When a line throws an error it drops to my catch block and displays an error message, etc. However, when debugging I need to know exactly what like
|
| Errors in Error List with no line numbers | 02 Jul 2009 00:03 GMT | 4 |
I'm having a problem with an ASP.NET website created in Visual Studio 2005 (using C#) where the debugger can identify that there are errors preventing it from compiling but it won't show the filename or the line number that generated the error. I'm going bananas trying to figure it
|