Plan System Requirements for Workflow Analyzer Development - rpapub/WatchfulAnvil GitHub Wiki
Caution
Content needs proof-reading.
This page documents all system requirements and installation steps needed to prepare a development environment for building custom Workflow Analyzer rules for UiPath Studio.
It serves as the foundation for all subsequent learning artifacts in the HelloWorld Rule Authoring milestone.
Important
This Development Environment setup must be completed before attempting to build or pack custom rules in UiPath Studio. These Getting Started instructions are tested and verified to work with the versions listed below.
Component | Supported / Recommended Version |
---|---|
Operating System | Windows 10 or 11 (x64) |
UiPath Studio | Community or Enterprise, version 2021.10 or later |
.NET SDKs |
.NET Framework 4.6.1 Developer Pack .NET 6.0 SDK .NET 8.0 SDK |
Visual Studio |
Visual Studio 2022 Community Edition Visual Studio 2022 Enterprise Edition Workloads: .NET Desktop Development
|
Download the installers from the official sites, as linked above.
- Required workloads:
- โ
.NET Desktop Development
- โ
- Run the installer with Administrator privileges.
The individual images of this sequence can be found here. Use the browser's back button to return to this page.
Caution
Community Edition must not be used in most enterprise settings. A commercial license is likely required โ review license terms carefully.
- Go to
Tools
โNuGet Package Manager
โPackage Manager Settings
. - Under
Package Sources
, click the + button. - Enter source details**:
- Name: UiPath-Official
-
Source:
https://uipath.pkgs.visualstudio.com/Public.Feeds/_packaging/UiPath-Official/nuget/v3/index.json
- Click OK to save and close the dialog.
The individual images of this sequence can be found here. Use the browser's back button to return to this page.
- Needed only for legacy rule targeting scenarios. If you are planning to use Workflow Analyzer to analyze even a single "legacy" project, then you need this.
- Run the installer with Administrator privileges.
The individual images of this sequence can be found here. Use the browser's back button to return to this page.
- Download from: https://dotnet.microsoft.com/en-us/download/dotnet
- Run the installer for the .NET 6.0 SDK with Administrator privileges.
The individual images of this sequence can be found here. Use the browser's back button to return to this page.
- Run the installer for the .NET 8.0 SDK with Administrator privileges.
The individual images of this sequence can be found here. Use the browser's back button to return to this page.
- It is assumed that you already have UiPath Studio installed.
After installation, confirm your setup with the following steps:
dotnet --version
Expected result:
- The command should print a version number, e.g.
9.0.x
, but more importantly, it should exit without errors. - No need to compare the versions shown in the output; just verify that the command runs successfully.
dotnet --list-sdks
Expected output includes:
6.0.x [C:\Program Files\dotnet\sdk]
8.0.x [C:\Program Files\dotnet\sdk]
To confirm .NET Framework 4.6.1 is installed:
-
Open Settings Press
Windows + I
. -
Navigate to Installed Apps
- Go to
Apps
โInstalled apps
.
- Go to
-
Search for ".NET Framework"
- Type
.NET Framework
in the search bar. - Look for:
- Microsoft .NET Framework 4.6.1 SDK
- Microsoft .NET Framework 4.6.1 Targeting Pack
- (Optional) Targeting Pack (ENU)
- Type
๐ธ Example:
To confirm Visual Studio is working:
-
Launch Visual Studio Use the Start Menu or desktop shortcut.
-
Open a Solution
- Go to
File โ Open โ Project/Solution
. - Select any
.sln
file.
- Go to
-
Check for Errors
- Ensure there are no missing SDK/component warnings.
To confirm required environment variables are available:
-
Check
DOTNET_ROOT
- This should point to the base directory where .NET SDKs are installed.
-
Inspect
%ProgramFiles%\dotnet
- This directory should contain one or more installed SDK folders.
-
Locate the active .NET CLI
-
Run the following command in your terminal:
where dotnet
-
This will show the path your system uses to invoke the
.NET
CLI.
-
Tip
If the command returns no results, check that the .NET SDK is properly installed and your PATH
variable is configured correctly.
Once your environment is set up and verified, you can proceed to:
- Fork and open the HelloWorld rule template project
- Learn how to build, pack, and deploy your first rule
โก๏ธ Continue with: Setup and Verify