# False Quality Risks Analysis

## Problem <a href="#problem" id="problem"></a>

We can see Unexpected QR in Sealights dashboard for a DotNet application on methods from files that were not changed for a long time.

## Solution <a href="#solution" id="solution"></a>

Please follow the below instructions:

1. Get a **binary artifact** (EXE, DLL) that was created **before the QR was reported** (ideally, the reference build)
2. Get a **recent artifact** that has a **QR on an unmodified code** (ideally, the latest build)
3. Download a **Decompiler tool called ILSpy** (open source, MIT license, free) from <https://github.com/icsharpcode/ILSpy/releases>

   <figure><img src="https://4057366433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjqTCMRYvHhDgsdPLUnc%2Fuploads%2FHRy7tCgF4PsikbSDdCPh%2Fimage-20210527-104421.png?alt=media&#x26;token=8cbb723d-00bc-49ad-ae68-36d30d5308a0" alt=""><figcaption></figcaption></figure>
4. Open the tool and drag the earlier artifact (1) to it, then locate a method that was reported as QR.
   1. Its contents will be visible on the right column.
   2. In the toolbar change the language from C# (default) to IL, and make note of the result (better - save it to a file)
5. Do the same for the later artifact (2), and compare the results.

&#x20;

We expect (4) and (5) to differ, please share with us the detailed information from this tool to help you understand why that change occurred.