> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/.net-.netcore/false-quality-risks-analysis.md).

# 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&amp;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.

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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/.net-.netcore/false-quality-risks-analysis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.