> 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/it/comandi-powershell/new-udsyntaxhighlighter.md).

# New-UDSyntaxHighlighter

New-UDSyntaxHighlighter esegue il rendering del codice con colorazione della sintassi in base al linguaggio e numeri di riga opzionali in una dashboard di PowerShell Universal.

### Sinossi

Evidenziazione della sintassi per il testo.

### Sintassi

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

### Descrizione

Evidenziazione della sintassi per il testo.

### Parametri

#### -Id

L'ID di questo componente.

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

#### -Code

Il codice di cui evidenziare la sintassi.

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

#### -Language

Il linguaggio con cui evidenziare il codice.

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

#### -Style

Lo stile da applicare al codice.

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

#### -ShowLineNumbers

Se mostrare i numeri di riga.

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

#### Parametri comuni

Questo cmdlet supporta i parametri comuni: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable e OutVariable. Per maggiori informazioni, veda [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Output

### Esempi

#### Esempio 1: evidenziatore di sintassi di base

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

Un evidenziatore di sintassi di base.

#### Esempio 2: stile

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

Un evidenziatore di sintassi con uno stile.

#### Esempio 3: numeri di riga

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

Un evidenziatore di sintassi con i numeri di riga.


---

# 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/it/comandi-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.
