UiPath Studio 支持您创建以下类型的项目：
- “流程”- 设计并发布自动化流程，以便机器人可以执行该流程。
- Library - Design workflows as reusable components and publish the project as a library that can be added as a dependency to multiple processes. For more information, see About Libraries.
- Test Automation - Design a test automation project. For more information about test automation, see the Test Suite section.
- Template - Design a process and publish it as a template that other processes which share common characteristics can then be based on. For more information, see Project Templates.
要创建新的空白项目，请转到“主页”（Studio 后台视图）>“开始”，然后在“新建项目”下选择要创建的项目类型。或者，您可以从“从模板新建”下的其中一个默认模板开始，或转到“模板”选项卡以浏览来源多样的更多模板。
在新项目窗口中，为每个项目配置以下内容：
- 为新项目输入名称（最多 128 个字符）和描述，以概括您打算如何使用此自动化项目（最多 500 个字符）。
- 选择创建项目的位置。创建项目的默认位置为
%USERPROFILE%\Documents\UiPath。 - Select the compatibility and language.
Note: The compatibility and language cannot be changed after you create a project. However, you can convert your Windows - Legacy projects to the Windows compatibility.
默认情况下，项目文件夹包含以下文件和子文件夹：
- Files
Main.xaml- Created by default to hold your main workflow. In addition, all the other automation XAML files you add to the project are stored in the project folder. Optionally, you can set a different file as main. All the files must be linked through the Invoke Workflow File activity to the file set as main or to a file marked as an entry point to the project. For test automation projects, aTestCase.xamlfile is created by default instead ofMain.xaml.project.json- 包含有关自动化项目的信息。
- Subfolders
.entities- 如果项目中使用了实体，则包含有关从 Data Service 导入的实体的数据。.local- 包含为项目在本地缓存的数据。
Note: The .localfolder is hidden. You can enable viewing hidden items from the Windows File Explorer settings..objects- 如果项目中使用了添加到对象存储库的任何项目，则包含与此等项目相关的数据。.project- 包含添加到项目中的标签。.screenshots- 如果在项目中使用了任何用户界面自动化活动，则包含在此等活动中生成的参考截图。.settings- 包含运行时使用的活动项目设置。.templates- 包含添加到项目中的文件模板。.tmh-如果在项目中使用了任何测试用例，则包含与此等用例相关的数据。
重要提示：
使用新版 Studio 创建的项目可能不适用于旧版 Studio。详情请参阅向后和向前兼容性。
You cannot use the following characters in file names: ", <, >, |, :, *, ?, \, /, ;. These characters come from Microsoft Windows restrictions and from other special character restrictions.
设置项目兼容性
创建新项目时，请根据要运行项目的环境选择兼容性：
- Windows - 使用具有 Windows 支持的 .NET 6。 这是默认选项。
- 跨平台 - 使用具有跨平台支持的 .NET 6。
- “Windows - 旧版”- 使用 .NET Framework 4.6.1。在 2021.10 之前的版本中使用的兼容性。
重要
- Windows 和跨平台流程需要 Orchestrator 2021.10 及更高版本才能运行。
- The Windows - Legacy option will no longer be available for new projects in the near future. We recommend selecting Windows or Cross-platform when creating a new project. You can convert your Windows - Legacy projects to the Windows compatibility.
To learn about the differences between compatibilities, see the following table. To find out more about the design experience in each compatibility, see Designing Automations.
| Windows - Legacy | Windows | Cross-platform | |
|---|---|---|---|
| Process execution | 32-bit | 64-bit | 64-bit |
| Supported platforms for execution | Windows (32-bit and 64-bit) | Windows (64-bit) | Windows, Linux, and macOS (64-bit) |
| Processes are compiled when published | No. Published packages contain the project source files. | Yes. Published packages contain compiled DLL files. | Yes. Published packages contain compiled DLL files. |
Only the activities packages that support the selected compatibility can be installed from the package manager.
每个项目的兼容性显示在 Studio 状态栏的右侧和“项目”面板>“依赖项”节点中。在“主页”（Studio 后台视图）>“开始”选项卡的“打开最近的项目”列表中，每个项目的条目中也会显示兼容性。
设计跨平台项目
跨平台项目使您能够创建不需要用户交互的自动化，以及使用 Chrome 的网页浏览器自动化。跨平台自动化可以在 Windows 和 Unix 这样的操作系统（例如 Linux 和 macOS）上执行。
要创建具有跨平台支持的无人值守项目，请执行以下操作：
- 在 Studio 中创建一个新项目，然后选择“跨平台”兼容性选项。此选项适用于所有项目类型。对于将 VB 语言用于表达式的流程，您可以选择在 Studio 和 Studio Web（目前在预览版中提供）中工作。
- 设计自动化。请注意，并非所有活动包都与跨平台项目兼容，因此包管理器中仅提供一些包。详细了解跨平台项目的设计体验。
跨平台项目的默认依赖项包括：- 在 Studio 配置文件中：UiPath.System.Activities、UiPath.Testing.Activities、UiPath.WebApi.Activities 和 UiPath.UIAutomation.Activities。
- 在 StudioX 配置文件中：UiPath.System.Activities、Microsoft Office 365、Google Workspace 和 UiPath.UIAutomation.Activities。
- 测试自动化。我们建议使用远程调试在将运行自动化的计算机上测试自动化程序，该调试程序适用于 Windows 机器人、Linux 机器人和 macOS 机器人。
- 在测试完自动化后，请将项目发布到 Orchestrator。Windows、macOS 和 Linux 运行 Unattended 作业的过程相同。
重要提示：
此版本的 Studio 与 Studio 2022.4 或更早版本中提供的旧版跨平台活动包版本不兼容。如果您在 Studio 2022.10 之前的版本中创建了跨平台项目，则在 Studio 2022.10 或更高版本中编辑它们之前，请将已安装的包更新为最新版本。某些属性可能无法再进行编辑。
在 Studio 和 Studio Web 之间切换
备注：
当前 Studio Web 处于预览阶段。
如果您想直接从浏览器中通过任何设备随时随地设计跨平台项目，则可以将项目添加到云中，并在 UiPath Automation Cloud 中的自动化设计器 Studio Web 中进行编辑。将项目添加到云端时，系统始终会同步更改，从而使您可以在桌面和网页之间无缝切换，并从上次中断的地方继续操作。
要与 Studio Web 兼容，跨平台项目必须满足以下要求：
- 项目类型为流程。
- 表达式的语言是 VB。
- 该项目包含单个工作流文件。
当项目与 Studio Web 兼容时，状态栏右侧会显示“与 Cloud 兼容”标签。要使项目在 Studio Web 中可用，请单击标签，然后选择“保存至 Cloud”。
备注：
Studio Web 不支持将 C# 语言用于表达式的项目。如果在 C# 项目中选择“保存至 Cloud”，则会发生错误。
将项目保存到 Studio Web 后，状态栏中的标签将更改为“云项目”。单击标签以打开一个下拉菜单，其中包含用于管理项目的选项：
- 保存至 Cloud - 将您在 Studio 桌面版中所做的最新更改保存到 Studio Web 中的项目。如果远程项目有更改，则必须首先确认是否想要覆盖更改。如果项目已在 Studio Web 中打开，则无法保存至 Cloud。
- 在 Studio Web 中打开 - 在 Studio Web 中打开项目。
- 保存副本 - 将当前项目在本地另存为新项目。您可以编辑名称，选择保存位置，并输入项目说明。
- 获取最新版本 - 获取您在 Studio Web 中所做的最新更改。如果远程项目和本地项目之间存在差异，则必须首先确认是否要覆盖本地版本。
同样，在 Studio Web 中创建项目时，您可以选择继续在 Studio 中工作。在 Studio Web 的“项目”页面中，打开项目右侧的菜单，然后选择“在桌面版中打开”。
在桌面上保存并关闭云项目时，所做的更改也会保存在远程项目中。当您在桌面上打开云项目时，该项目将使用云端的最新更改进行更新。在这两种情况下，如果本地项目和远程项目之间存在差异，系统均会提示您确认，然后再继续。
设置项目语言
在 Studio 配置文件中创建新项目时，您可以选择用于表达式的语言（VB 或 C#）。VB 是默认选择的语言，但您可以转到“主页”（Studio 后台视图）>“设置”>“设计”，将 C# 设置为新项目的默认语言。在 StudioX 配置文件中创建的项目使用 VB.NET 语言编写表达式。
不支持在同一项目中同时使用 VB 和 C# 表达式。无法在 C# 工作流中使用 VB 表达式，反之亦然。在复制其他项目中的活动、调用或导入工作流时，请确保其使用的语言与目标项目相同。
您可以将 C# 库安装为 VB 项目中的依赖项，反之亦然。但是，无法从安装库的项目访问使用语言特定的表达式为库项目中的参数定义的默认值。
C# 局限性
- 当前的 C# 实现基于使用 C# 版本 5 的 C# 编译器，因此限制了对诸如合并分配、null 条件运算符、null 合并运算符、字符串插补等新功能的访问。
- 包含带增量表达式的项目无效。
- 包含
nameof()运算符的表达式被标记为无效，并且当前 C# 实现中不允许使用。 - 包含对带可选参数方法的调用的表达式必须包含可选参数的值。
- 与 VB.NET 相比，C# 项目的设计时间和运行时性能较低。当运行时性能至关重要时，我们建议使用 VB.NET 而不是 C#。
设置项目版本
语义版本控制
语义版本控制方案采用 Major.Minor.Patch[-Suffix] 格式，其中：
- Major 是主要版本。
- Minor 是次要版本。
- Patch 是补丁版本。
- -Suffix（可选）是连字符加一串句点分隔的标识符，紧接在补丁版本后。这表示预发行版本。
标识符必须仅由 ASCII 字母数字和连字符组成，并且不得为空。数字标识符不得以零开头。此外，内部版本元数据必须通过以下方式表示：附加一个加号及一串以句点分隔的标识符，紧接在补丁版本或预发行版本后面，例如 1.0.0-alpha+1。
在新建流程或库时，默认版本方案是语义版本。可以从“发布”窗口中更改，只需在版本号中添加额外一位数字即可。项目的语义版本可也从 project.json 文件修改。版本号为 major.minor 的项目将自动添加补丁编号 0。
传统版本控制
为项目生成的传统版本号采用 M.m.bbbb.rrrrr 格式，其中：
- M 表示主要版本。
- m 表示次要版本。
- bbbb 表示内部版本。
- rrrrr 表示修订版本。
也可以在 project.json 文件中编辑主要版本和次要版本，而内部版本和修订版本是根据某种算法生成 - 内部版本值是指自 01.01.2000 以来经过的天数。修订值是当天至发布时所经过的秒数。其结果除以 2，使得最大的修订编号不会超过 65535。
“发布”窗口中的建议版本号基于项目的以往版本控制方案生成，对于采用 4 位数版本控制方案的项目则考虑使用当前的日期和时间戳。
管理项目
“项目”面板可用于查看当前项目的内容，添加文件夹，打开文件位置，管理依赖项，以及调整项目设置。
将文件资源管理器中的文件直接复制并粘贴到“项目”面板。您还可使用拖放功能对一个或多个文件执行相同操作，包括 .xaml 工作流。您还可以使用 Ctrl + C 和 Ctrl + V 快捷键或上下文菜单中的“复制”和“粘贴”选项来复制面板内的文件或文件夹。
您可以双击小于 10 MB 的 TXT、CS、VB、JSON（不包括 project.json 文件）和 XML 文件，在 Studio 中使用文本编辑器进行编辑，并突出显示语法。
| Option | Description |
|---|---|
Expand All | Expands all nodes in the automation project. |
Collapse All | Collapses all nodes in the automation project. |
Refresh | Refreshes the project. |
Show All Files | Shows all files belonging to the automation project, including the project.json. |
File Explorer | Opens the project's location on the machine. |
Project Settings | Opens the Project Settings window for processes or libraries. |
项目的上下文菜单
右键单击“项目”面板中的任意位置以打开上下文菜单，其中包含下表中所述的选项。选项的不同子集是否可用，取决于您在面板中的右键单击位置、项目类型以及是否将项目添加到来源控件。
| Option | Description |
|---|---|
| Open Project Folder | Opens the local folder containing the project. |
| Project Settings | Opens the Project Settings window for adjusting project preferences. |
| Add | Opens a list of items that can be added to the project: folder, sequence, flowchart, state machine, global handler, workflow, or, in test automation projects, test case. Use workflow to create a workflow file based on built-in templates (sequence, flowchart, state machine) or local file templates. |
| Import Files | Opens the File Explorer window to import files into your project. By default, the *.xaml filter is applied to list only workflow files, but you can change it to all files to import other file types. Imported is added to the imported file name if it coincides with the name of a workflow from the current project.You can only import workflow files that use the same language for expressions as the current project. When you import a workflow file, the dependencies of the current project are compared to the ones in the source project file, if one is available. If there are any discrepancies, the Import Workflow window is displayed with information about changes needed to avoid unresolved activities. Available dependency updates are selected by default and are installed when you select Import. The icon  indicates a missing dependency that should be installed.The icon  indicates a newer version used in the source project that you should update to.The icon  is displayed if a missing dependency is not available for the current project, or if the available version is different than the one in the source project.Optionally, you can indicate a project.json file to use as a reference and select whether to search in prerelease package versions. |
| Convert to Windows | In a Windows - Legacy project, opens the Convert to Windows window where you can convert the project to the Windows compatibility. |
| Extract as Library | Extracts a process or test automation project as a library. |
| Add to Source Control | Adds the current project to source control using Git Init, Copy to Git, Add to TFS, or Add to SVN options. Please note that this option is only visible when right-clicking the project node. When a project is added to source control, additional options are available in the context menu. See the options for GIT and the options for SVN and TFS. |
| Open | Opens the selected files using the default program. |
| Open File Location | Opens the local folder containing the file. |
| Rename | Enables you to rename the selected file or folder, and opens the Rename Item window. The item is renamed in all occurrences. Note: The full path of the new file must not exceed 258 characters. |
| Copy | Copies the selected files or folders to the clipboard. You can then paste them in the project panel or in the Windows file explorer. |
| Paste | Pastes files or folders that were copied to the clipboard. |
| Delete | Deletes the selected item only from your local machine. |
| Select for Compare | Selects the current file for comparison. |
| Compare with Selected | Compares the current file with the previously selected file using Compare Files. |
| Find References | Finds all references to the file in the project. The results are displayed in the Find References panel. |
| Open in Text Editor | Opens the selected text file in a text editor inside Studio in read-only mode. To open a text file in edit mode, double-click it. You can double-click TXT, CS, VB, JSON (excluding the project.json file), and XML files smaller than 10 MB to edit them inside Studio in a text editor with syntax highlighting. |
| Debug File | Debugs the selected .xaml file. |
| Set as Main | Sets the selected .xaml file as Main in the project definition, meaning that the project execution starts with that file. There can only be one Main project file. The name of the file set as main appears in bold in the Project panel. |
| Activity Layout | Open the Properties window for files in library projects, where you can customize the design of the generated activity. |
| Set as Global Handler | Sets the .xaml file as the Global Exception Handler for the project. This is applicable to one workflow per project/process. |
| Remove Handler | Removes the Global Exception Handler tag from the .xaml file. |
| Enable Entry Point | Marks the selected workflow file as an entry point for the process, making it possible to select it as the workflow to run first when using the Invoke Process and Run Parallel Process activities in other processes, or when starting a job from Orchestrator. Notes: When a file is marked as an entry point, an arrow is displayed on the icon next to the file name  .Enabling a file that is ignored from publishing as an entry point sets the file as publishable. This option is not available for test case files. This option is not available in library projects. |
| Disable Entry Point | No longer marks the selected workflow file as an entry point for the process. This option is not available for the workflow file that is set as Main. |
| Extract as Template | Saves the selected workflow or test case as a template on which you can then base other files in the project. Using a file template allows you to save time when you need to create multiple files with the same structure. When you add a new workflow or test case, you have the option to base it on any template of the same type that exists in the Templates project folder. |
| Ignore from Publish / Set as Publishable | Marks one or more selected files as excluded from publishing or publishable. Notes: When a file is ignored from publishing, the icon next to the file name turns gray  .Ignoring a file marked as an entry point from publishing disables the entry point. These options are not available for workflow files in library projects. In projects where XAML files are compiled when published, workflow and test case files that are excluded from publishing are not compiled. |
| Make Private / Make Public | Marks one or more selected files in a library project as private or public, A private workflow file is included in the published package, but no reusable component is created and made available in the Activities panel in projects where the library is installed as a dependency. Notes: When a file is marked as private, the icon next to the file name turns gray .These options are not available for test case files. |
| Create Test Case | Creates a test case that invokes the selected workflow file. |
| Convert to Test Case / Convert to Workflow | Converts the selected workflows to test cases or the selected test cases to workflows. |
| Import Test Cases | Imports test cases into the project as draft test cases. |
| Add Test Data | Opens the Import Data Variation Source window that enables you to add test data to the project. This option is only available for test cases. |
| Link to Test Manager | Opens the Link to Test Manager window that enables you to link the selected test cases to Test Manager. |
| Run Test Cases / Debug Test Cases | Runs or debugs multiple selected test cases. |
GIT 的上下文菜单选项
在添加到 GIT 存储库的项目中，“项目”面板中的每个文件旁边都会显示一个图标，以指示文件状态：
The file is synced with the repository.
The file has been modified.
The file has been added.
Right-click a file or project node in the Project panel to open the GIT-specific context menu for Managing Projects with GIT.
| Option | Description |
|---|---|
| Commit | Commits current changes to the local GIT repository. |
| Push | Pushes the current version onto the remote repository. |
| Pull (rebase) | Pulls remote files and rebases the current branch. |
| Manage Branches | Opens the GIT window with options for managing currently added branches. |
| Show Changes | Opens the File Diff window for comparing changes between the local version and the remote version of the file. |
| Show History | Opens the Show History window for comparing two versions of the same file. |
| Undo | Opens the Undo Pending Changes window if the file was not committed or pushed to the remote repository. |
| Copy Repository URL | Copies the repository URL of the project to the clipboard. |
SVN 和 TFS 的上下文菜单选项
在添加到 SVN 或 TFS 存储库的项目中，“项目”面板中的每个文件旁边都会显示一个图标，以指示文件状态：
The file is not checked out for editing.
The file has been checked out for editing.
The file has been edited.
The file has been added.
Right-click a file or project node in the Project panel to open the context menu with options specific to managing projects with TFS or SVN.
| Option | Description |
|---|---|
| Open | Opens the selected .xaml file in the Designer panel, in read-only mode if it was not checked out for edit from the TFS/SVN repository. |
| Rename | Enables you to rename the selected file or folder, and opens the Rename Item window. When checking in the renamed .xaml file, the previously modified version must also be checked in. |
| Delete | Deletes the selected item only from your local machine. The latest checked in version of the file is still available in the TFS/SVN repository. |
| Check Out For Edit | Marks the selected file or folder as locked for editing. Checking out a file locks it on the server so that no one else can edit it. |
| Finish Editing | Checks in the project.json file in the respository, together with changes and a commit message. |
| Add | Uploads the selected item to the TFS/SVN server. This option is not available, if the item was previously uploaded to the server. |
| Get Latest Version | Downloads the latest version of the selected item from the TFS/SVN repository. |
| Show changes... | Opens the File Diff to compare changes between the versioned file and the one mapped locally. |
| Check In | Displays the Check In Changes window and enables you to upload the selected item to the server as the newest version. The .xaml file must be saved before uploading it. After it’s checked in, the file becomes read-only in Studio. |
| Undo | Displays the Undo Pending Changes window and enables you to Revert the changes done to the project, either revert modified files to previous or unversioned states, or retrieve files which were deleted from the local machine. Changes cannot be reverted after the file was checked in. |
| Run | Runs the selected workflow, even if it's not checked out or added to the repository. |
| Set as Main | Sets the selected .xaml file as Main in the project. The first created .xaml is set as Main by default. |
| Copy Repository URL | Copies the repository URL of the project to the clipboard. |
调整项目设置
A set of individual settings can be established for each automation project that you’re working on. Such settings are available in the Project Settings window, which can be opened by clicking the 
in the Project panel.
设置窗口字段说明
The following table describes the project settings for process, test automation, and template projects. For information about the settings available for libraries, see About Libraries.
| Field | Description |
|---|---|
| Name | Change the name of the project. Such names may contain whitespace characters. When naming projects, keep in mind that whitespace characters are removed at publish time. This field accepts up to 128 characters. |
| Description | Change the project description. This field accepts up to 500 characters. |
| Project tags | You can add one or more tags to the project, either by creating new ones or by reusing tags already defined in Orchestrator. There are two types of tags: labels and properties (key-value pairs). Tags are included in the published package and they help describe and categorize projects. For example, they can refer to the automated application (an Excel label) or the department (a department:accounting key-value property).When you start typing, possible matches are suggested from already defined tags, and you can reuse one by selecting it from the list of matches. For a property match, the key followed by the : (colon) character is displayed first, and the associated values are displayed after you select the key,To add a new tag, after you enter the name, click the entry with the plus sign next to the name. Separating strings with the : (colon) character enables you to add properties, while entries that don't contain a : add labels.Labels and key-value properties are limited to 256 characters. Tag names can't contain these characters: <, >, %, &, \, ?, /, :.Project tags can be automatically applied to processes in Orchestrator. For more information about using tags, see Organizing resources with tags in the Orchestrator guide. |
| Automation Hub URL | URL of an Automation Hub idea linked to the project. For more information, see Linking a Project to an Idea in Automation Hub. |
| Package Icon | Optionally, define a custom icon for the project. You can browse to and select a file, or enter a path or public URL to a jpeg, jpg, or png file up to 1MB in size.After the project is published, the icon is displayed as follows: For processes, in the Assistant next to the process name, making it easier to identify it in the list of processes. For templates, next to the template in Home (Studio Backstage View) > Templates. For libraries, next to the package in the Manage Packages window in Studio. The icon is not visible in Manage Packages if a local file is used for a library published to Orchestrator or a feed that does not support embedded icons, In this case, specify the icon using a URL. |
| Disable Pause | Enable or prevent users from pausing execution from the UiPath Assistant. Set to Yes if pausing the process during execution would result in crashing it. For example, if an activity in your workflow uses the Timeout property, pausing the execution might cause the timeout to expire, thus breaking the execution. |
| Attended Automation | Set to Yes to indicate that the project should only be executed in an attended context. Use this setting for projects that include UI Automation activities or other activities that require user interaction. |
| Starts in Background | Set to Yes to turn the project into a Background Process and allow it to run in the background concurrently with other processes, as long as it does not use UI interaction. |
| Supports Persistence | Set to Yes to turn the project into an Orchestration Process. |
| PiP Options | Indicate whether the project was tested using Picture in Picture (PiP) and whether it should start in PiP by default. Tested for PiP usage; Starting in PiP - The automation has been approved to run in PiP mode. When run, it starts in PiP by default. Tested for PiP usage; Not starting in PiP by default - The automation has been approved to run in PiP mode. When run, it starts in the main session or desktop by default. Not tested for PiP usage - The automation has not been approved to run in PiP mode. When run, it starts in the main session or desktop by default. If run in PiP, a dialog informs the user it was not tested using this feature and prompts for confirmation before proceeding. |
| PiP Type | Select how to isolate the automation from the user session when running the project in PiP: New Session (child session on the machine) or New Desktop (virtual desktop in the user session). |
单击“确定”，所做的更改即可在“项目”面板和 project.json 文件中查看。
Check out the Configuring Activity Project Settings page to read about how to adjust activity properties at project level.
备注：
请注意，每当要将一个序列中的大量活动复制到另一个序列时，我们均建议您事先向下滚动到“设计器”面板底部。这是因为 Windows Workflow Foundation 限制的关系。
删除未使用的项目资源
不必要的资源会使项目更难以理解并影响性能。为避免此问题，请通过单击 Studio 功能区中的“删除未使用的资源”，选择要删除的内容，以从项目中删除未使用的资源：
- 工作流 - 删除项目中未引用的工作流文件。
- 变量 - 删除当前已打开文件中未使用的变量。
- 参数 - 删除当前已打开文件中未使用的参数。
- 依赖项 - 删除项目中未使用任何活动的已安装活动程序包。
- 导入 - 删除当前已打开文件中未使用的已导入命名空间。
- 屏幕截图 - 删除项目中任何活动未使用的信息截图。
3 天前更新