Analyzer dependencies showing as unresolved full paths

Steps to reproduce:

1. Create a new .NET Core Console App
2. Add a package reference to xunit.analyzers
3. Build the solution
4. Close the solution
5. Re-open the solution
6. Expand the project’s dependencies node
7. Notice there is no Analyzers node
8. Modify whitespace in the project file and save it (triggering a design-time build)
9. Notice an Analyzers node appears with unresolved child, which is a full path rather than the analyzer’s name
10. Close and reopen the solution and the analyzers appear correctly
11. Modify the project file again (stays resolved)
12. Close and re-open the solution (stays resolved)
13. Build from VS then close/re-open solution and notice Analyzers node is missing again

Open questions:

• Why is the Analyzers node not initially present? This seems to happen if the build before opening the solution happened within VS.
• Why are analyzers appearing as paths and in unresolved state?

[drewnoakes]

This has been fixed and will be released in 16.5.

[drewnoakes]

This can be reproduced more easily by:

1. New ASP.NET Core Web Application (empty)
2. Close solution
3. Reopen solution

Deleting the .dtbcache file in the .vs folder between steps 2 and 3 fixes the problem, so the DTB caching in ProjectServices is looking like the culprit here.

---

EDIT The above worked for me five times in a row, but no longer does. It doesn’t seem that deterministic. Running VS in the debugger makes it fail more often. Right now I’m Ctrl+F5’ing and can’t repro it at all.