Repository navigation
pdb's no longer being packaged in the non symbols package - #1403
Conversation
|
Why that change? |
|
basically, if the pdb's are in the non-symbols package, VS won't download the symbols package for debugging. |
|
as far as I can tell, the Travis build was already borking on that test. |
|
So now we put the pdbs in the normal package, but not into the symbols
|
|
Other way around. |
|
But not everyone is using symbols packages. What about the other case?
|
|
depends if you want strict nuget replication in that area or not. Nuget doesn't package them in the non-symbols regardless. Should only require a small tweak to fix for when there is no symbols requested. Depends on what you'd like to do? |
|
I think we should still put the pdbs in the normal package when we don't
|
|
No it doesn't, tho i'll confirm that. In the case that you want to add them, you can still add it as a file dependency and it won't be removed. (I've just confirmed that that is true of that build) |
|
Confirmed. Nuget does not include pdb's regardless of whether symbols have been requested or not. |
|
Ok. Let's remove them then. But how about a template file property that
|
|
not a bad idea? so for project files only? meaningless for file templates. |
|
yes that would be awesome |
|
do you want that as part of this pull request or another? |
|
please add it to this one. |
|
done |
|
travis failing on the same tests. It has an ignore on it, so not sure why it gets run. |
pdb's no longer being packaged in the non symbols package
No description provided.