Does pdb file contain source code

NET project. You could try using dia2dump to look at the contents. Everything else is contained in the binary itself, including the names of all types, members and function arguments. Source: PDB files: what every developer must know.

The PDB-files also include all comments of your source files. Net compiler versions can embed the full source code with all comments in the PDB file. The free JetBrains dotPeek decompiler uses this Blob to show the decompiled code. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. How much information do pdb files contain?

NET Ask Question. Asked 12 years, 10 months ago. Active 9 months ago. Viewed 9k times. Is it wise to redistribute the pdb files along with a commercial application?

Improve this question. Did you have any success yet? I am aiming for the same goal of "patching" the source file locations of an existing PDB.

Dawodo No. Add a comment. Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. A symbol server won't really help here. Symbol servers serve up PDB files, not source files. They are used to distribute PDB files. BTW your nightly builds should always generate new build s otherwise you don't know what day's build you're running.

Personally the automated builds we run increment the build the last number every night before compilation. The paths you gave are CM paths unless you were just using symbolic names so they are irrelevant.

The file paths are used in the PDB. Then the PDBs would refer to this path. Now, if a developer happens to have this same directory layout then the source files would be picked up automatically. If not then they will have to go point to the correct source. I believe this is a necessary evil in your case because how does a developer know what source goes with what assembly? I, in general, do not believe in putting built binaries into CM as I believe it complicates things.

The only exception is third-party components which I don't build. In that case the source code is irrelevant. When I do use third-party components I tend to isolate them outside the scope of any project to: a make it easier to update, and b keep the size of the repository down. Now the platform assemblies are isolated and a project can use the appropriate version. The advantage is that if you update the version binaries the project will automatically get the update. Finally a developer could be working on multiple projects and versions simultaneously without conflict.

The content you requested has been removed. Ask a question.