> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/fr/commandes-powershell/new-udsyntaxhighlighter.md).

# New-UDSyntaxHighlighter

New-UDSyntaxHighlighter affiche du code avec une coloration syntaxique adaptée au langage et des numéros de ligne facultatifs dans un tableau de bord PowerShell Universal.

### Résumé

Coloration syntaxique pour le texte.

### Syntaxe

```powershell
New-UDSyntaxHighlighter [[-Id] <String>] [[-Code] <String>] [[-Language] <String>] [[-Style] <String>] [-ShowLineNumbers] [<CommonParameters>]
```

### Description

Coloration syntaxique pour le texte.

### Paramètres

#### -Id

L'ID de ce composant.

```
Required?                    false
Position?                    1
Default value                [Guid]::NewGuid()
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Code

Le code dont la syntaxe doit être colorée.

```
Required?                    false
Position?                    2
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Language

Le langage dans lequel colorer le code.

```
Required?                    false
Position?                    3
Default value                powershell
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Style

Le style à appliquer au code.

```
Required?                    false
Position?                    4
Default value                oneDark
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -ShowLineNumbers

S'il faut afficher les numéros de ligne.

```
Required?                    false
Position?                    named
Default value                False
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### Paramètres communs

Cette applet de commande prend en charge les paramètres communs : Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable et OutVariable. Pour plus d'informations, consultez [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Sorties

### Exemples

#### Exemple 1 : Coloration syntaxique de base

```powershell
New-UDSyntaxHighlighter -Code 'Write-Host "Hello World"' -Language powershell
```

Une coloration syntaxique de base.

#### Exemple 2 : Style

```powershell
New-UDSyntaxHighlighter -Code 'Write-Host "Hello World"' -Language powershell -Style 'vs'
```

Une coloration syntaxique avec un style.

#### Exemple 3 : Numéros de ligne

```powershell
New-UDSyntaxHighlighter -Code 'Write-Host "Hello World"' -Language powershell -ShowLineNumbers
```

Une coloration syntaxique avec des numéros de ligne.


---

# 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.devolutions.net/powershell-universal/fr/commandes-powershell/new-udsyntaxhighlighter.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.