Ben Adams

> target .net4.0 as it is the last Long Term release Are you thinking 4.5.2? Support for .NET 4.0, 4.5, 4.5.1 ended last year on January 12, 2016

Yes and the CI runs the tests for `net46`+, `netcoreapp2.1`, `netcoreapp3.1` and `net5.0` 

Released a new version that doesn't have this issue; though not sure it makes it a sensible type name, looking into that

Not sure it particularly worth the $499 per year?

These methods won't come out in the trace ``` at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() ```

The `ResolvedMethod` on the `EnhancedStackFrame` has most of the tokens as its what builds up the method as you can see from its [`Append` method](https://github.com/benaadams/Ben.Demystifier/blob/master/src/Ben.Demystifier/ResolvedMethod.cs#L38-L145) and you can enumerate them...

If you can; I was able to resolve them in some situations but not others. If specified in method signature it would resolve e.g. `List AddToList(List, int)` If not specified...

Why specifically source only? Not too familiar with their advantages

Was wondering how name collisions worked: ```csharp #if PUBLIC_FLUID_CACHING public #else internal #endif ``` So src package uses `internal` and library uses `public`?

@dennisdoomen do you have an example of how/where you'd use it; then I can expose it correctly...