PdbProject is massively useful with our large portable project that gets built with our own build system. Visual Studio has always been our chosen editor and debugger on Windows, and now with PdbProject we get Intellisense, F12 and family in that environment as well.
(Please can we have a version for Visual Studio 2013!)
I am getting similar problem like James. I have installed the 2.1 and I am getting a message box saying,
"Cloud not load pdb file <pdb_filename>
Debug Reason: CoCreateInstance
I have run my VS as administrator.
Is there any way to get proper TFS integration with a generated solution? Currently, files that are under source control in a solution that is not checked in WILL get the "Source Control" right-click menu within a source code tab, but NOT when using the Solution Explorer.
This is also an issue with other solution/project generators (such as CMake).
... please consider making this a library or external .exe so we can run this in batch against a collection of pdbs. I would like to pass in a list of paths to pdbs I want, any mappings necessary, and have the output passed back as a list of vcxproj xml documents, which I can then post-process using additional code that would grab linker information from my dirs, sources, and makefiles, such that I can then update the vcxproj files with additional information to get a working build. I've been working on migrating a large code base from CoreXT to MSBuild for a while, and this would help me a lot if I could use it in the middle of my chain of transformations. I am starting out with an empty default Win32 vcxproj, for example, and building from there ... instead of the empty default, I could use the vcxproj generated from using this tool. However, manually opening each PDB is not as useful as being able to do things in batch and have some way to programmatically interact with the tool.
I notice that the target type is always set to exe ... is this information not available in the pdb?
Thanks for putting this out. It should save me a lot of time. Although it's not perfect, and won't totally replace all my work to migrate this by hand with partial automation, it certainly will help me ensure all the compiler switches are correct when I complete migration.
Actually, I see that I can easily reference PdbProject.dll and ProjectCreator.dll from the VS extensions folder where PdbProject.vsix was installed, and do something like this:
var l = new PDBLoader();
var i = l.Load(args);
var moduleItem = l.GetModuleItem(i);
var includePaths = moduleItem.GetIncludePaths();
This is great! So, I can grab switch from the pdbs I want directly and feed that into my conversion transformations which I've already written. :))
I'm excited to try this out -- it would really help my project that is built using scons.
What version of Visual Studio does this support? I have VS2013 Professional installed but the installer says "This extension is not installable on any currently installed products." It doesn't mention what installed products the extension would install on.
I have encountered a bug where the extension will not open PDBs using capital letters .PDB for the file extension. However, if I rename the PDBs to .pdb the extension opens the file without issue.
Using: Windows 7 Enterprise with Visual Studio 2012 Professional