Chris Ventura

So far our discussions have only covered what you can see in #689. We are currently focusing on addressing other instrumentation gaps and usability issues, but we welcome any thoughts,...

What I've run into is something similar to the following. Consider the following code. ``` MyMethod(bool setting1 = true, bool setting2 = false) MyMethod(Settings settings) class Settings { bool Setting1...

> I would prefer optional parameters, but they must be always named. It's much easier to search for `MyMethod.*setting2:\strue` than track the reference trail. Searching only works when the parameters...

Some of the work with this issue involves investigating if there are other options, in addition to the binding redirects. For now we're simplifying things so that .net core and...

> Any other reports of this one? I've only seen it once. During the SIG meeting we decided to keep this issue around and tentatively scheduling looking into it after...

One thing that I do not like about this approach, based on the current functionality in that feature, is that it requires someone to drop a file in a particular...

The native code has the ability to run before any managed code is loaded/executed. In particular the initialization code of the profiler runs before any managed code is loaded, and...

This issue might be dependent on #968.

I think that we should leverage the ideas in proposal 1. I think that it will be quicker to build and easier to maintain. To prevent some of the dependency...

I think that it's a good idea to at least run a subset of the integration tests on Alpine. Most of the bugs that I've encountered when supporting native profiler...