pdb-files

I want my application to be distributable as a single .exe file but I want to be able to get nice error reports with source code line numbers (the application simply sends email with exception.ToString() and some additional information when unhandled exception occurs). Is there any way to embed .pdb into assembly? Use MiniDumps instead of "exception.ToString()". It will give you a lot more information and does not need the .pdb to be distributed with the .exe. Useful Link: Post-Mortem Debugging Your Application with Minidumps and Visual Studio .NET I have used the following AssemblyResolve

When adding a DLL as a reference to an ASP.Net project, VS2008 adds several files to the bin directory. If the DLL is called foo.dll, VS2008 adds foo.dll.refresh, foo.pdb and foo.xml. I know what foo.dll is :-), why does VS2008 add the other three files? What do those three files do? Can I delete them? Do they need to be added in source control? Source Control: Ben Straub said in a comment to this post: The .dll.refresh files should be added to the source control if required, while the .xml , .pdb and of course the .dll files should not be added. John Rudy explained when to add the .refresh

I am getting confused as to what is the difference between the compiler and linker PDB files respectively (i.e. in Visual Studio, Project Properties > C/C++ > Output Files > Program Database File Name vs Project Properties > Linker > Debugging ) . I have tried to find the answer online and so far I know (may be wrong) that a PDB file by the compiler is generated for obj files while the PDB file by the linker is generated for the binary (exe or dll) and is the one used for debugging. If that is not true, please explain the difference. Either way, what to do when I am creating a DLL where I have

I need something that can generate a PDB from a DLL file (C# .NET code), is there any free program to do that? You need the source code in order to generate a PDB. Even you have no sources and code obfuscated, you can create pdb by recompile with ildasm and ilasm: decompile assembly by ildasm : ildasm /out=assembly_name.il assembly_name.dll complile with ilasm : ilasm assembly_name.il /dll /pdb Stelio Actually you can do it also with dotPeek from 1.2 version onward. Right click the assembly in Assembly Explorer, and select "Generate Pdb". It also has the option to generate files for referenced

How can you read the source paths used to compile a pdb in .NET (C#) environment? Yahia The PDB format is NOT documented - but there is an API from MS called DIA which provides several methods to deal PDB. It is COM-based... for details see MSDN . PDB files usually contain filenames and linenumbers BUT I am not sure that they always contains full path to the source. Some interesting information on PDBs can be found here . IF you want some .NET source code dealing with .PDBs see Mono.Cecil and esp. the namespace Mono.Cecil.Pdb . 2/12/16 update Microsoft has been open-sourcing the PDB format.

I have a weird problem with PDB files in a VS 2013 C# project. Basically what is happening is that the PDB files are not getting rebuilt when the project is getting rebuilt. This is causing the project to always think it needs to get rebuilt. I've tried cleaning the solution, but if anything changes in the project it gets put back into the same state again. I created a simple class library project and the behavior was the same. As a sanity check, I created the same class library on another PC and it worked as I would have expected. Does anybody have any ideas as to what might be causing this

Is it possible for the debugger (or the CLR exception handler) to show the line where the exception happened in Release mode using the pdb? The code, in release mode, is optimized and do not always follow the order and logic of the "original" code. It's also surprising that the debugger can navigate through my code step by step, even in Release mode. The optimization should make the navigation very inconfortable. Could you please clarify those two points for me? I'm not as familiar with how this is done with CLR, but it's probably very similar to how it's done with native code. When the