Search code examples
visual-studionugetdebug-symbolsfakeiteasy

Visual Studio tries to load FakeItEasy symbols from Z:\Builds\work

I was running a unit-test in Visual Studio today using FakeItEasy. I was offline and found the following symbol-loading to be happening and taking a long time:

FakeItEasy symbol loading

My question is, where does the path Z:\Builds\work\... come from and why is Visual Studio trying to load symbols from that path. Could it be that this path corresponds to the CI that the binaries were built on? If so, is it a thing that the maintainer of the library should fix, or something that I must locally configure? I am using the FakeItEasy 1.25.2 binaries that I fetched via NuGet.

I am aware of the fact that you can disable symbol loading (e.g. see this question), but actually I want the symbols to be loaded if possible.

Solution

  • Yes, Z:\Builds\work\… is the path from which TeamCity builds FakeItEasy.

    I'm not a big symbol user, so am not sure what you want "fixed". Why are you loading the symbols, and what behaviour would you expect in this case? If we push the symbols to SymbolSource.org you'd still need to be online to access them, no?

    Can you give an example of a NuGet package that behaves how you'd like? How does it behave in your situation?