# 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 [#finding-issues](https://docs.sonarsource.com/sonarqube-for-visual-studio/using/investigating-issues#finding-issues "mention") article for more information.

The [investigating-issues](https://docs.sonarsource.com/sonarqube-for-visual-studio/using/investigating-issues "mention") 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="https://1613591589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5CSDwdOaYoOAGYNiRqgl%2Fuploads%2Fgit-blob-cb21246c200ee571fdf2f8aa3e458b6e3b972d52%2F63f0c47b758a67a7674f37726c1962b5976bb9de.png?alt=media" 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="https://1613591589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5CSDwdOaYoOAGYNiRqgl%2Fuploads%2Fgit-blob-7e7ed4eb02028b6fe016d51c64437c00d927e243%2F3255f43f379678a80a2287d19de09d1a600f03bf.png?alt=media" 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="https://1613591589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5CSDwdOaYoOAGYNiRqgl%2Fuploads%2Fgit-blob-c4b2191f76508430d6f7aeb4fc1a7daf8fe9315e%2Fcc0fdfa9acd1e0be96f79240416a1052b6f6594c.png?alt=media" 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](https://docs.sonarsource.com/sonarqube-for-visual-studio/using/rules "mention") 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 [#javascript-and-typescript-analysis](https://docs.sonarsource.com/sonarqube-for-visual-studio/resources/troubleshooting#javascript-and-typescript-analysis "mention") troubleshooting article about problems related to memory usage.