Options
Feature request: Symbol Server & Source Server support?
swythan
Posts: 12
As mentioned here, it would be nice to have symbol server & source server support. I've got a different reason, though.
Firstly, it could occasionally be handy to see info from the BCL reference sources, which would require both symbol server (to get the PDB files) and source server (to get the source files) support. I can't see that being massively useful, though, as I can't optimise those functions, so all I really care about is whether or not the function itself is expensive.
What I would find useful would be to use our internal source server set-up to retrieve source files from subversion.
We've got our automated build split into several packages, which each generate binaries (& symbols) that dependant packages can fetch. In the end we have a build that fetches all the binaries and builds an installer (and a separate one for the symbols). All the symbol files that are generated are annotated with information about the svn path & revision of the source files (using SourceServerSharp).
That all means that we can be working on one of the higher level projects (e.g. the application GUI) and still debug into the low-level components. Visual Studio uses the info in the pdb files to transparently fetch the correct source files from subversion. Note that this is actually a lot better than using svn myself, as it knows what svn revision matches the binary I'm using (technically the pdb).
If ANTS Profiler could do that, it would be very cool. I've no idea if the mechanism used to retrieve the sources is available in a MS library or not, though. If not, I suspect it might not be worth the bother re-implementing it, but if it is then it would be quite handy.
Firstly, it could occasionally be handy to see info from the BCL reference sources, which would require both symbol server (to get the PDB files) and source server (to get the source files) support. I can't see that being massively useful, though, as I can't optimise those functions, so all I really care about is whether or not the function itself is expensive.
What I would find useful would be to use our internal source server set-up to retrieve source files from subversion.
We've got our automated build split into several packages, which each generate binaries (& symbols) that dependant packages can fetch. In the end we have a build that fetches all the binaries and builds an installer (and a separate one for the symbols). All the symbol files that are generated are annotated with information about the svn path & revision of the source files (using SourceServerSharp).
That all means that we can be working on one of the higher level projects (e.g. the application GUI) and still debug into the low-level components. Visual Studio uses the info in the pdb files to transparently fetch the correct source files from subversion. Note that this is actually a lot better than using svn myself, as it knows what svn revision matches the binary I'm using (technically the pdb).
If ANTS Profiler could do that, it would be very cool. I've no idea if the mechanism used to retrieve the sources is available in a MS library or not, though. If not, I suspect it might not be worth the bother re-implementing it, but if it is then it would be quite handy.
Comments