szehetner

I couldn't reproduce the error on my machine. Could you post the output of `dotnet --info`? Does it work with .NET Framework (select "NetFramework" as preferred runtime in Tools->Inlining Analyzer->Options)?

I was finally able to reproduce this and think I found the cause. The published assemblies contained a reference to a wrong path, so this only worked if you happened...

Sure, you can ask questions here or tag me in issues in your repository. There is probably not too much you can reuse directly from the Inlining Analyzer, but at...

Do you get any errors in the Inlining Analyzer Output Window? I took a simple highlighting extension as a starting point, but I can't find the link now. There is...

As you have already guessed in the other ticket, F# is not supported. Running the analyzer and getting the inlining information from the JIT compiler is language independent, but for...

I have never tried it with a code analyzer, but you are right, the issue looks similar to #11. I can't debug it right now, but could you try to...

The issue with the `m1[i]` invocation was that ref returns for properties and indexers where not handled correctly. This should be fixed now. This sample worked for me with x64...

I think I can reproduce the issue. Looks like a bug with the handling of multiple installed .Net Core versions. I don't have a fix yet, need to investigate this...

I could get it to work with 2.x runtimes, but not with 3.1, so this is something you could try: Open "Tools" -> "Inlining Analyzer" -> "Options" and specify a...

Are you sure you have a 2.1.0 runtime installed? You can check which runtimes you have by running `dotnet --info` and look for all "Microsoft.NetCore.App" versions. These are the ones...