Adam Sitnik

Is the generated code using a fully qualified type name (#1009) when referring to `CancelationToken`?

> Conclusion: by default, BenchmarkDotNet correctly processes transitive dependencies for most NuGet packages. However, in some corner cases (as described above), the generated project doesn't inherit some of the references...

> I believe when https://github.com/dotnet/BenchmarkDotNet/issues/1403 is solved it will solve this as well. So it can be linked and closed at the same time as the other linked issues. Sounds...

I am supportive of this idea. Please go ahead and send a PR.

I am surprised that it ever worked (in the past we were attaching the debugger in a way it was performing full suspend of the debugged process, suspending yourself ==...

It's possible that ClrMD does not include types emitted on the fly in reported types list. Have you tried using the VS Disassemby Window: https://learn.microsoft.com/en-us/visualstudio/debugger/how-to-use-the-disassembly-window?view=vs-2022?

@leculver thank you!

I believe we should simply drop the support for old runtimes that are not supported for years. Users can still benchmark them, if they need a dissasembly they simply need...

> I'm not entirely sure it will work The solution that I am proposing here was recommended in https://github.com/dotnet/BenchmarkDotNet/issues/2371#issuecomment-1814709479 by @ViktorHofer who is the MSBuild expert on the .NET Team....

We should reconsider writing the code analyzers for BDN, similar to what xUnit provides.