- Visão geral
- Introdução
- Conceitos
- Usando o UiPath CLI
- Guias de instruções
- Receitas de CI/CD
- Referência de comando
- Visão geral
- Códigos de saída
- Opções globais
- Agente de código uip
- codificador UIP
- Contextualização da uip
- Documento da UIP
- Função UIP
- Proteções da UIP
- configuração-llm-uip
- gateway-llm-uip
- criação do uip Maestro
- Registro do uip Maestro
- hub de modelo da uip
- Atividades Localizar
- atividades get-padrão-xaml
- Analisar
- lista de regras do analisador
- Criar
- Limpeza
- instalação de entidades-de-dados
- lista de entidades de data-fabric
- comparação dos arquivos
- obter-repositório-objeto-da-Biblioteca
- obter-objeto-repositório
- Init
- lista de instâncias
- Empacotar
- inspeção de pacotes
- Instalação dos pacotes
- versões dos pacotes
- Publicar
- Remoto
- restore
- executar, depurar e adicionar; Execução
- Configurações
- Início do Studio
- pesquisa de modelos
- adição de dados de teste
- adicionar-fila-de-dados-de-teste
- adição-variação dos dados de teste
- TM
- UIA
- Validar
- fluxo de trabalho-exemplos obter
- lista de exemplos de fluxo de trabalho
- tarefas do UIP
- anexo
- Campo personalizado
- Defects
- Execuções
- exportar trabalhos
- Migração
- Rótulo do objeto
- Empacotar
- cenário-perf
- grupos de carga do cenário-perf
- dados de execução do cenário-perf
- relatório do cenário-perf
- Projeto
- permissões do projeto
- Prompts
- Relatar
- Requisitos
- Resultado
- Executar
- Agendamentos
- Log de caso de teste
- Casos de teste
- Conjuntos de Testes
- Log de etapa de teste
- Usuário
- Aguardar
- Traces da UIP
- Feedback de traces da uip
- Migração
- Referência e suporte
uip codedapp convert
Syntax and options for `uip codedapp convert`, which converts an exported VB low-code app (`.uiapp`) into a React and TypeScript coded app on your machine.
uip codedapp convert converts an exported Visual Basic (VB) low-code app into a React and TypeScript coded app that you own. The input is the .uiapp file that Apps Studio exports for a VB app — a standalone low-code app whose expressions are written in VB, the Apps Studio default. The command accepts .uiapp files only.
The result is a Vite, React, and TypeScript project with:
- One component per page
- Typed data access through
@uipath/uipath-typescript - A
conversion-report.jsonthat lists what converted, what did not, and the cause of each gap (converter,source-app, orby-design)
The conversion runs on your machine. It makes no tenant call and needs no uip login.
Pré-requisitos
The converter binds the app's VB expressions with the Roslyn compiler, which runs on .NET, so the .NET 10 Runtime must be installed on the machine that runs convert. The .NET SDK is not needed.
The runtime for each operating system is available from dotnet.microsoft.com. Once it is installed, dotnet --list-runtimes in a new terminal prints a line that starts with Microsoft.NETCore.App 10.. Other .NET versions can stay installed.
Without the runtime, convert stops before it reads the file and reports CONVERT_PREREQUISITE_MISSING.
Converter SDK
The converter, @uipath/codedapp-convert-sdk, ships with the tool. If the command reports that the converter SDK could not be loaded, for example after an install with --omit=optional, uip tools install codedapp reinstalls the tool together with the SDK. uip tools update does not help here, because the installed tool version is already current.
You can also install the SDK beside the tool with npm install -g @uipath/codedapp-convert-sdk@beta, without -g for a project-local CLI.
Resumo
uip codedapp convert <file> [options]
uip codedapp convert <file> [options]
Argumentos
| Argumento | Description |
|---|---|
<file> | Required. The exported VB low-code app: a .uiapp file. |
Opções
| Bandeira | Description |
|---|---|
--out <dir> | Output directory for the coded app, by default ./<file name> in the current directory. An empty value is refused instead of treated as omitted. |
--force | Convert into a non-empty directory, for a re-conversion. uipath.json and node_modules are kept. |
--refresh | Bind every expression again instead of reusing the output directory's bind cache. |
Saída
The coded app goes to --out, or to a directory named after the file in your current directory. The output includes:
README.mdconversion-report.jsonconversion-log.ndjson- The
fix-converted-appskill
The fix-converted-app skill
The output holds the fix-converted-app skill as a skill source, in the same layout as UiPath/skills: .uipath/agent-skills/skills/fix-converted-app/SKILL.md. convert runs no agent itself. It prints the command that installs the skill under NextSteps:
uip skills install --repo ./.uipath/agent-skills --path .
uip skills install --repo ./.uipath/agent-skills --path .
When run from the output directory, the command installs the skill for every coding agent detected on the machine, or for one agent only with --agent <name>. Refer to uip skills. The skill then starts from the coding agent, by its name.
The skill reads conversion-report.json, works through the issues the report blames on the converter by editing the generated code, builds the project to check its work, and writes what it did to conversion-fixes.md. It never changes the report or the log. The skill reads the generated code against the export as well as the report, so it can take minutes and can change things the report did not list.
Exemplos
# Convert an export; the coded app lands in ./expense-app
uip codedapp convert ./expense-app.uiapp
# Choose the directory
uip codedapp convert ./expense-app.uiapp --out ./apps/expense
# Re-convert into the same project after a converter update (uipath.json is kept)
uip codedapp convert ./expense-app.uiapp --force --refresh
# Convert an export; the coded app lands in ./expense-app
uip codedapp convert ./expense-app.uiapp
# Choose the directory
uip codedapp convert ./expense-app.uiapp --out ./apps/expense
# Re-convert into the same project after a converter update (uipath.json is kept)
uip codedapp convert ./expense-app.uiapp --force --refresh
Formato dos dados (--output json)
A conversion with no gaps:
{
"Code": "ConvertCompleted",
"Data": {
"Path": "./expense-app",
"Kind": "uiapp",
"Pages": 3,
"Files": 58,
"Report": {
"Issues": 0,
"Converter": 0,
"SourceApp": 0,
"ByDesign": 0
}
}
}
{
"Code": "ConvertCompleted",
"Data": {
"Path": "./expense-app",
"Kind": "uiapp",
"Pages": 3,
"Files": 58,
"Report": {
"Issues": 0,
"Converter": 0,
"SourceApp": 0,
"ByDesign": 0
}
}
}
A conversion with gaps also carries the skill install command:
{
"Code": "ConvertCompletedWithGaps",
"Data": {
"Path": "./apps/expense",
"Report": {
"Issues": 2,
"Converter": 2,
"SourceApp": 0,
"ByDesign": 0
},
"Skill": {
"Install": "uip skills install --repo ./.uipath/agent-skills --path ."
}
}
}
{
"Code": "ConvertCompletedWithGaps",
"Data": {
"Path": "./apps/expense",
"Report": {
"Issues": 2,
"Converter": 2,
"SourceApp": 0,
"ByDesign": 0
},
"Skill": {
"Install": "uip skills install --repo ./.uipath/agent-skills --path ."
}
}
}
The examples are trimmed. The full Data carries these fields:
| Campo | Description |
|---|---|
Path | The directory the coded app was written to. |
Kind | The input type: uiapp or uis. |
Outcome | converted, converted-with-gaps ou cannot-run. |
Pages | The number of pages converted. |
Files | The number of files written. |
Kept | The existing files the run left in place, such as uipath.json. |
Expressions | Counts of expressions: referenced, emitted, exact, and lenient. |
Unconverted | Counts of expressions and event handlers that did not convert. |
Blocking | The number of diagnostics that stopped behavior from converting. |
Report | The path of conversion-report.json and its issue counts. |
Skill | The fix-converted-app skill: Path, Source, and Install. |
NextSteps | The commands to run next. |
Results and exit codes
Result and Code say what the numbers mean, so they, not the counts, are the values to branch on:
Result | Code | Sair | Significado |
|---|---|---|---|
Success | ConvertCompleted | 0 | Everything converted. Nothing in the report is blamed on the converter. |
Success | ConvertCompletedWithGaps | 0 | The project builds and runs, with gaps: Report.Converter is 1 or more, or expressions or event handlers are unconverted. Refer to The fix-converted-app skill. |
Failure | ConvertOutputCannotRun | 1 | The project is written but cannot run as it is: a blocking diagnostic stopped behavior from converting, or generated TypeScript does not parse. Data still carries the result. |
Failure | CONVERT_* | 1 | Nothing was converted. Refer to Conversion failures. |
Conversion failures
Code | ErrorCode | Causa |
|---|---|---|
CONVERT_FILE_REQUIRED | invalid_argument | No file was passed. |
CONVERT_FILE_NOT_FOUND | not_found | The file does not exist. Apps Studio exports the file. |
CONVERT_UNSUPPORTED_TYPE | invalid_argument | The file is not a .uiapp export. |
CONVERT_NOT_A_DIRECTORY | invalid_argument | The output path exists and is not a directory. |
CONVERT_DIR_NOT_EMPTY | invalid_argument | The output directory is not empty, and --force was not passed. |
CONVERT_OUT_EMPTY | invalid_argument | --out was passed an empty value. |
CONVERT_SDK_UNAVAILABLE | configuration_error | The converter SDK could not be loaded. Refer to Prerequisites. |
CONVERT_PREREQUISITE_MISSING | configuration_error | The .NET 10 Runtime is missing. Refer to Prerequisites. |
CONVERT_INPUT_REJECTED | invalid_argument | The converter could not read the export. |
Relacionado
- uip codedapp push — upload the converted app to Studio Web.
- uip codedapp pack — package a built coded app into a
.nupkg. - uip codedapp init — start a coded app from a template instead.