bytecode

It would be helpful if the lcov generated reports could generate relative paths. My use case is that I am generating coverage reports from a docker image and then using VS Code Coverage Gutters which supports relative paths to view the coverage. But it doesn't work because the absolute paths on the docker c

Below a list of all opcodes currently supported by the CIL emulator of Echo's AsmResolver back-end.

If no --testProjectName option is given it would be nice that faultify scans the current folder for a project file. This way you can just run faultify from the test project folder if you want to and not have to specify the csproj that is right there.

When outputting signature of entry point method as CIL assembler code, it should be marked with .entrypoint directive.

Example code:

using System;
using System.Reflection;
using CilBytecodeParser;

class Program
{    
    public static void Main(string[] args)
    {
        Console.WriteLine(CilAnalysis.MethodToText(MethodBase.GetCurrentMethod()));
        Console.ReadKey();