{"action":"created","issue":{"url":"https://api.github.com/repos/GitTools/GitLink/issues/97","repository_url":"https://api.github.com/repos/GitTools/GitLink","labels_url":"https://api.github.com/repos/GitTools/GitLink/issues/97/labels{/name}","comments_url":"https://api.github.com/repos/GitTools/GitLink/issues/97/comments","events_url":"https://api.github.com/repos/GitTools/GitLink/issues/97/events","html_url":"https://github.com/GitTools/GitLink/issues/97","id":177248263,"number":97,"title":"ReadMe.md Documentation Questions/Clarifications","user":{"login":"mesheets","id":16882600,"avatar_url":"https://avatars.githubusercontent.com/u/16882600?v=3","gravatar_id":"","url":"https://api.github.com/users/mesheets","html_url":"https://github.com/mesheets","followers_url":"https://api.github.com/users/mesheets/followers","following_url":"https://api.github.com/users/mesheets/following{/other_user}","gists_url":"https://api.github.com/users/mesheets/gists{/gist_id}","starred_url":"https://api.github.com/users/mesheets/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mesheets/subscriptions","organizations_url":"https://api.github.com/users/mesheets/orgs","repos_url":"https://api.github.com/users/mesheets/repos","events_url":"https://api.github.com/users/mesheets/events{/privacy}","received_events_url":"https://api.github.com/users/mesheets/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-09-15T18:10:38Z","updated_at":"2016-09-16T03:53:46Z","closed_at":null,"body":"I have been trying out GitLink, and it seems to fill a needed role in enabling Symbol Server / Symbol Store integration capabilities when using a Git-based version control repository.  In working through this, I have a few questions/clarifications related to the ReadMe.md.\r\n\r\n\r\n> GitLink makes symbol servers obsolete\r\n\r\nThis would not appear to be universally true; rather, it would seem this is only true in scenarios where the PDB symbol files can be deployed with the assemblies.  Symbol servers are still needed in scenarios where the PDB symbol file is not available (e.g. \"attach to process\" debugging of a deployment that must exclude symbol files).  Unless the PDB files are also deployed (which is not always allowable/possible/etc.), a symbol server would seem necessary.\r\n\r\nAdditionally, is it really GitLink that makes the symbol servers unneeded, or is it rather the inclusion of the symbol files in the NuGet packages?  It would seem that it is the inclusion of the symbol files in the NuGet packages and not GitLink, as this packaging approach is not limited to GitLink and can be used with version control repositories supported by the built-in indexing.\r\n\r\n\r\n> Running for an uncommon / customized URL\r\n\r\nBased on testing, there appear to be some problems when file/revision information is provided via the URL query string instead of the URL path.  This appears to be a limitation of the Windows Debugging Tools and not GitLink, though this limitation should probably be noted as an aid to other GitLink users.\r\n\r\nThe URL format with the out-of-the-box GitWeb configuration specifies the file and revision in the URL query string, and the Windows Debugging Tools can't seem to handle this.  The [GitWeb \"read me\"](http://repo.or.cz/git/gitweb.git/blob_plain/HEAD:/gitweb/README) notes that this can be changed by enabling PATH_INFO"},"comment":{"url":"https://api.github.com/repos/GitTools/GitLink/issues/comments/247512469","html_url":"https://github.com/GitTools/GitLink/issues/97#issuecomment-247512469","issue_url":"https://api.github.com/repos/GitTools/GitLink/issues/97","id":247512469,"user":{"login":"mesheets","id":16882600,"avatar_url":"https://avatars.githubusercontent.com/u/16882600?v=3","gravatar_id":"","url":"https://api.github.com/users/mesheets","html_url":"https://github.com/mesheets","followers_url":"https://api.github.com/users/mesheets/followers","following_url":"https://api.github.com/users/mesheets/following{/other_user}","gists_url":"https://api.github.com/users/mesheets/gists{/gist_id}","starred_url":"https://api.github.com/users/mesheets/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mesheets/subscriptions","organizations_url":"https://api.github.com/users/mesheets/orgs","repos_url":"https://api.github.com/users/mesheets/repos","events_url":"https://api.github.com/users/mesheets/events{/privacy}","received_events_url":"https://api.github.com/users/mesheets/received_events","type":"User","site_admin":false},"created_at":"2016-09-16T03:53:46Z","updated_at":"2016-09-16T03:53:46Z","body":"I appreciate the follow up.\r\n\r\nWith deploying PDBs, hasn't deploying them always been an option to avoid symbol server setup?  To add some detail to some scenarios alluded to the original post, in some contexts such as security-sensitive or government work, deployment of symbols is forbidden.  In other situations, bandwidth/size considerations might preclude deployment of symbols to clients.  Perhaps to frame the question another way, is symbol server still needed when the symbols cannot be deployed side-by-side?  While pdb files could be saved to a network share, etc., it wouldn't seem to be as convenient as just going ahead and using symbol store, which does the correlation automatically when initiating a debug session?\r\n\r\nRelated to the build setup with which I've primarily been working, while the source in hosted in an external (non-TFS) Git repository, TFS Team Build is used to generate the builds.  I have a command build step that does the GitLink indexing, followed by the out-of-the-box build step to index and publish symbols (albeit with the indexing action disabled, since GitLink is needed in order to properly handle that aspect).  I suppose that Team Build build step does make it easier to use symbol server than if building via some other tool without such support provided out-of-the-box.\r\n\r\n\r\nIf my experience with the Windows Debugging Tools in handling query string parameters seems consistent with the experience of others, I can give a look at creating a pull request."}}
{"actor":{"display_login":"mesheets"}}