# Running an analysis

Now that you’ve installed the SonarQube for IDE extension in your IDE, running an analysis is straight-forward. For the most part, new analyses are automatically triggered when you open a file, as you type, or with each file save following a change in the code. Below we’ve outlined other ways to trigger a SonarQube for IDE analysis.

## Triggering an analysis <a href="#triggering-an-analysis" id="triggering-an-analysis"></a>

First, open a project containing C#, VB, C++, JavaScript, or TypeScript files. New issues will be reported when you type, open, or save a file. Issues are highlighted in your code and also listed in the **Error List** tool window; see the [Investigating issues](/sonarqube-for-visual-studio/using/investigating-issues.md#finding-issues) article for more information.

The [Investigating issues](/sonarqube-for-visual-studio/using/investigating-issues.md) page has all the details you need to know about recognizing SonarQube issues in your IDE.

## Analysis results <a href="#analysis-results" id="analysis-results"></a>

The status bar indicates that an analysis is running and will update when (the analysis is) finished:

<div align="left"><figure><img src="/files/QvSEq7eoDXo9NDE7QOLy" alt="The Visual Studio status bar will update when SonarQube for Visual Studio has finished the analysis." width="563"><figcaption></figcaption></figure></div>

Issues are highlighted in your code and also listed in the **Error List**. Sonar Rule descriptions appear when you hover over code that triggered an issue:

<div align="left"><figure><img src="/files/c0EAqCLo15IgCbiFz9eg" alt="Hover over an issue, identified by the squiggles, to see the Sonar Rule description." width="563"><figcaption></figcaption></figure></div>

To get a detailed description, click the error code or right-click the error in the **Error List** and select **Show Error** **Help**.

<div align="left"><figure><img src="/files/Iz80V3v72yNeNvxwr9x9" alt="Select an error from the list and choose Show Error Help to bring up the detailed rule description."><figcaption></figcaption></figure></div>

For details on managing rules, see the [Rules and languages](/sonarqube-for-visual-studio/using/rules.md) page. It will also include details about parameterizing Roslyn analyzers.

### Language-specific analysis

#### JavaScript and TypeScript analysis <a href="#javascript-and-typescript-analysis" id="javascript-and-typescript-analysis"></a>

If you’re experiencing issues when analyzing TypeScript or TypeScript, check this [Troubleshooting](/sonarqube-for-visual-studio/resources/troubleshooting.md#javascript-and-typescript-analysis) troubleshooting article about problems related to memory usage.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-for-visual-studio/getting-started/running-an-analysis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.