This is a really great video. It helped me bridge understanding from reading a large number of outdated articles online. Creating our own symbol server like this should work for my needs for the time being. Neither Azure Devops Artifacts nor JFrog Artifactory support snupkg and I've struggled to find a way to share the pdb's in an automatic way to other developers in my organization. Source Link is cool, but it might be worth mentioning here that even with it's large number of supported source control vendors there are some pretty basic limitations that I'm running up against... in the large corporation where I work we have our own self-hosted Enterprise Github which uses active directory for auth. This does not work today with Source Link and Visual Studio 2019 (or it simply doesn't work with ours). This pushes me right back to where I was before... I can share out the symbols now but I can't provide the source code unless I bundle it in the main nuget package. If anyone has another option I'm all ears. I'm just trying to make it easy within my organization to use a series of "common" nuget packages, debugging included.
Well, I upgraded to the latest git client, switched to using git-credential-manager-core, logged into our Enterprise Github via the web and added a Personal Access Token using roles to keep it's access narrow. Then I went into Debugger settings, and where you mentioned "Enable Source Link Support" I also enabled "Fall back to Git Credential Manager authentication...". With my personal access token enabled and using git-credential-manager-core, I can now successfully used Source Link in VS 2019 and GitHub Enterprise.
@@mphilmon Hi Matt, I'm happy to hear that you enjoyed the video and thank you for the valuable comments! Good to know that the "Fall back to Git Credential Manager authentication..." option could help in such cases.
This is a really great video. It helped me bridge understanding from reading a large number of outdated articles online. Creating our own symbol server like this should work for my needs for the time being. Neither Azure Devops Artifacts nor JFrog Artifactory support snupkg and I've struggled to find a way to share the pdb's in an automatic way to other developers in my organization. Source Link is cool, but it might be worth mentioning here that even with it's large number of supported source control vendors there are some pretty basic limitations that I'm running up against... in the large corporation where I work we have our own self-hosted Enterprise Github which uses active directory for auth. This does not work today with Source Link and Visual Studio 2019 (or it simply doesn't work with ours). This pushes me right back to where I was before... I can share out the symbols now but I can't provide the source code unless I bundle it in the main nuget package. If anyone has another option I'm all ears. I'm just trying to make it easy within my organization to use a series of "common" nuget packages, debugging included.
Well, I upgraded to the latest git client, switched to using git-credential-manager-core, logged into our Enterprise Github via the web and added a Personal Access Token using roles to keep it's access narrow. Then I went into Debugger settings, and where you mentioned "Enable Source Link Support" I also enabled "Fall back to Git Credential Manager authentication...". With my personal access token enabled and using git-credential-manager-core, I can now successfully used Source Link in VS 2019 and GitHub Enterprise.
@@mphilmon Hi Matt, I'm happy to hear that you enjoyed the video and thank you for the valuable comments! Good to know that the "Fall back to Git Credential Manager authentication..." option could help in such cases.