Menu
I have used VS 2010 and VS2008. When I used them with my WCF Service projects, my .PDB files were always copied when I did a Publish Web Site. Now, with VS2012, no PDB files are getting copied when I do a Publish Web Site. The PDB files ARE getting created for both Debug and Release but nothing happens when I do a Publish Web Site (for either Debug or Release).
I have searched this forum (and the Internet). My solution is as follows: 1) WCF Service Library project. 2) WCF Service Web Site
When I first did a publish, I had to create a profile and I did this.
When I right-click on the WCF Service Library project and select properties, I only get tabs for Application, Build, Build Events, Debug, Resources, Services, Settings, Reference Paths, Signing, WCF Options, Code Analysis. I do NOT get tabs for Package/Publish Web and other items that I used to get. I tried to right click on my WCF Service Web Site project and there is nothing in the Property Pages to indicate this.
I have even tried to add items to my .pubxml file and that does not work.
I wouldn't think I'd need to update my Debugging options to specify Symbols location. I would think that my Publish should just "do it" like it did in 2008 and 2010. Any advice?
Thanks In Advance.
903
The easiest way to use the PDB file is to let Visual Studio do the heavy lifting - either launch your program with Visual Studio's "Debug" command (F5 by default), or run the program and use the "Attach to Process" item in Visual Studio's Debug menu.
PDB files help you and the debugger out, making post-mortem debugging significantly easier. You make the point that if your software is ready for release, you should have done all your debugging by then.
Answers. PDBs are required for debugging and store debugging information and they are created when you compile the application. Unless you plan to debug in production there is no need and you should aim to deploy in release mode.
pdb file holds debugging and project state information that allows incremental linking of a Debug configuration of your app. The Visual Studio debugger uses . pdb files to determine two key pieces of information while debugging: The source file name and line number to display in the Visual Studio IDE.
In VS2012 Website publishing, symbols are always excluded by default. Why? It comes down to a design issue where website projects don't actually have a build configuration. If you look at the configuration manager in VS when your solution is in Release mode, the website project will always be in Debug mode; there are no other options. This is because website projects are not MSBuild based, and hence do not respect MSBuild configurations.
Instead, you can edit your .pubxml to tell it to include the symbols. Try adding this:
<PropertyGroup> <ExcludeGeneratedDebugSymbol>False</ExcludeGeneratedDebugSymbol> </PropertyGroup> For me this worked (in the publishing profile):
<PropertyGroup> ... <DebugSymbols>True</DebugSymbols> </PropertyGroup> Or using the publishing wizard:
20
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
