Each top-level folder is one NuGet package of Studio project templates. CI just runs
nuget pack <folder>/<Template>.nuspec — the published version is the <version> in the
nuspec, and everything beside the nuspec is swept into the package.
contentFiles/any/any/pt{N}/.local/template.json <- Studio metadata for this variant
contentFiles/any/any/pt{N}/{VisualBasic|CSharp}/ <- the project payload
Studio scans pt0, pt1, … until a gap, so a new variant is just the next index. There is no
manifest to register it in.
Legacy = net472, Windows = net8.0-windows, Portable = cross-platform. The field filters
the New Project wizard, it is not a default the user can override: the framework dropdown is built
from the distinct TargetFramework values across a package's pt* folders, and with only one the
user is locked to it. An absent field deserializes to Legacy.
The blank Main.xaml for each framework/language is maintained by Studio at
Studio/UiPath.Studio.Plugin.Workflow.Shared/ProjectTemplates/Blank/{framework}/{language}/.
Copy from there rather than hand-editing XAML; the Windows/Portable delta is only the
PresentationFramework/WindowsBase/PresentationCore references.
- Background-process templates omit
UiPath.UIAutomation.Activities. WithRequiresUserInteraction: falsethere is no interactive session, so UI automation cannot run. Applies to BackgroundProcess, OrchestrationProcess and LongRunningAutomation. Don't "fix" a dangling UIAutomation assembly reference by adding the dependency — remove the reference. - Legacy variants are pinned to the 24.10 activity line. 24.10 is the last LTS whose packages
still ship a
.NETFrameworkgroup; System 25.2.0, Excel 3.0.1, Mail 2.0.10 and WebAPI 2.3.0 dropped it. Newer pins will not restore on a Legacy project. - Cross-platform variants drop Excel and Mail — the activities that matter need the desktop
Office apps. Studio's own
Blank/Portabletemplate does the same. Exception: REFramework's cross-platform variants keepUiPath.Excel.ActivitiesbecauseTests/MainTestCase.xamlreadsTests.xlsxwith the file-based Workbook activities. - The payload must be a flat project, never a solution. Studio's New Project wizard creates
one project whose root is the destination folder: it writes
project.jsonthere fromtemplate.json, drops anyproject.jsonnested in the payload, and never opens a.uipx. A payload shaped as<name>.uipx+<name>/project.jsontherefore becomes one project rooted one level too high, and every project-relative Invoke Workflow File path breaks. Users get a solution by ticking Create in solution in the wizard. - Studio builds
project.jsonfromtemplate.json, not from the payload. The payload'sproject.jsonis replaced, so itsruntimeOptionsanddotNetVersionnever reach the user. SetRequiresUserInteractionintemplate.json(Studio's own Blank template does); when it is absent Studio defaults totrue(foreground). - Never set
DotNetVersionintemplate.json. It is theUiPath.Shared.DotNetVersionenum, and a Studio whose enum has noNet10(every release before .NET 10 support, e.g. the Windows LTS line) fails to deserialize the file; with the field in every variant it loads none of them and reports "The project template in package ... is not supported with the current Studio profile". Leave it out: the user picks the .NET version as Minimum Robot version in the New Project dialog (24.10 = .NET 8, the default when the field is absent; 26.10 = .NET 10). A .NET 10 project runs only on Robot 26.10+, so older robots and serverless reject itsproject.json. Studio builds that run on .NET 10 report CS1705 inCodedWorkflowsfor a .NET 8 Portable project; that is a Studio issue, worked around per project by choosing 26.10. - Ship agent guides under
Framework/, not at the payload root. Studio 26 writes its own genericAGENTS.mdandCLAUDE.mdinto every new project root (AgentInstructionFiles.Write, no existence check), overwriting the template's copies. - Release channels are
master/<Template>branches; work infeature/<target>/<name>.