Editing source path in “index sources” build template.
-
Tuesday, September 18, 2012 6:57 AM
Hi,
Do anyone if it is possible to change the destination filename in the pdb’s from the build template(vs 2010)?
When upgrading from the old Perl script to the built-in option in 2010 the destination filename changes from “MySourceFile.cs” to “MySourceFile;12343534.cs” (filename;changesetnumber.fileextension) in the pdb files causing issues both with source stepping(work almost but not quite as before) and with dump file debugging (doesn’t work at all).
With the dump file debugging visual studio will go get the file and but it locally but refuse to open it as(we believe) the filename isn’t the one it expects. You can’t even open the file manually as it has the wrong filename as the changeset number is added to the file name.
With normal source stepping it will get the file and show it but if you put a breakpoint and stop the debugger and press F5 the breakpoint will not be hit as the filename isn’t the correct one. Really annoying as you have to go to the repository and get the file manually else it won’t work.
If you run scrtool from debugging tools for windows on a PDB you can see the paths in the pdbs.
/Klavs
All Replies
-
Wednesday, September 19, 2012 6:32 AMModerator
Hi Klavs,
Thanks for your post.
Which issue you occurred? After changed the destination filename, TFS Build can’t build the solution?
Try to build your solution using VS 2010 and MSBuild manually, what’s the result?
John Qiao [MSFT]
MSDN Community Support | Feedback to us
-
Thursday, September 20, 2012 8:12 AMModerator
Hi Klavs,
Has this issue been resolved?
If you have any further research of this issue, please share your experience here.
John Qiao [MSFT]
MSDN Community Support | Feedback to us
-
Thursday, September 20, 2012 8:51 AM
No John it builds fine.
The problem is in the source paths burned into the pdb files as part of the build have changed.
Please re-read original post.
-
Thursday, September 20, 2012 9:12 AMModerator
Hi Klavs,
Thanks for your reply.
So, you think that issue caused by TFS or Team Building?
John Qiao [MSFT]
MSDN Community Support | Feedback to us

