Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider switching to portable PDB symbol files #447

Closed
stakx opened this issue Sep 21, 2017 · 1 comment · Fixed by #789
Closed

Consider switching to portable PDB symbol files #447

stakx opened this issue Sep 21, 2017 · 1 comment · Fixed by #789
Assignees

Comments

@stakx
Copy link
Contributor

stakx commented Sep 21, 2017

This is a reminder (not likely to be relevant before mid-2018) to check whether we can make the switch back to portable PDBs. We reverted (in #443) to classic Windows PDBs because of #428.

As mentioned in that issue, the main showstopper appears to be TFS. Microsoft will supposedly have fixed the issue in the 2018 version of TFS (as mentioned here).

@stakx stakx added this to the 4.10.0 milestone Jul 14, 2018
@stakx stakx self-assigned this Mar 10, 2019
@stakx stakx removed this from the 4.11.0 milestone Apr 3, 2019
@stakx
Copy link
Contributor Author

stakx commented Apr 3, 2019

This cannot go further as long as AppVeyor doesn't support .snupkg. (While we could put portable PDBs in the main package, doing some still bears the risk of interfering with some users' tools if they're not perfectly up-to-date (e.g. VSTS), and it's safer putting them in a symbols package.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant