C# exceptions not showing filename/line numbers (PDB issue?)
-
Hi, I'm developing an Explorer bar using VS.NET 2003 (C#) on Windows XP. For some time, I've noticed that I don't have filenames and line numbers appearing in my exceptions' stack traces. On the other hand, debugging with breakpoints, etc. seems to work fine in VS.NET 2003. I can't understand why this isn't working -- and I think it used to work, perhaps under VS.NET 2002, but maybe not. The information doesn't appear in exceptions when running under VS.NET or when not. I am running my Explorer bar (which is a class library, not an application) on the same machine (and user account) which built the library. The PDB file is accessible to me, and its location does match the location in the assembly. I am making Debug builds, and I do have "Generate debugging information" enabled. As far as I can tell, the PDB and DLL files are equally fresh and the same version? Any tips? Is this a known bug? It's driving me batty trying to locate an exception in code blocks without any help from line numbers. Thanks! Arun
-
Hi, I'm developing an Explorer bar using VS.NET 2003 (C#) on Windows XP. For some time, I've noticed that I don't have filenames and line numbers appearing in my exceptions' stack traces. On the other hand, debugging with breakpoints, etc. seems to work fine in VS.NET 2003. I can't understand why this isn't working -- and I think it used to work, perhaps under VS.NET 2002, but maybe not. The information doesn't appear in exceptions when running under VS.NET or when not. I am running my Explorer bar (which is a class library, not an application) on the same machine (and user account) which built the library. The PDB file is accessible to me, and its location does match the location in the assembly. I am making Debug builds, and I do have "Generate debugging information" enabled. As far as I can tell, the PDB and DLL files are equally fresh and the same version? Any tips? Is this a known bug? It's driving me batty trying to locate an exception in code blocks without any help from line numbers. Thanks! Arun
I had a problem like this when i downloaded and installed Borland's C# builder to check it out. It's installer reconfigured all of the debugging ide stuff to point at the borland stuff. It does ask though before doing this and warn you that debugging will not work in Visual Studio anymore. I would imagine that Borland Delphi 7 does the same thing. May or may not be your problem. If not 1 down x to go...
-
I had a problem like this when i downloaded and installed Borland's C# builder to check it out. It's installer reconfigured all of the debugging ide stuff to point at the borland stuff. It does ask though before doing this and warn you that debugging will not work in Visual Studio anymore. I would imagine that Borland Delphi 7 does the same thing. May or may not be your problem. If not 1 down x to go...
Actually, I figured it out. I had been using the GAC, and the DLL was expecting the PDB to be in the GAC, too. I copied the PDB to the same directory in the GAC, and that worked. Later, I decided to not use the GAC for development work. Thanks for responding!