Manage activity packages in Studio

Install, update and remove activity packages with the Package Manager, manage package sources, and repair a project's dependencies.

Every activity in Studio comes from an activity package, a NuGet package with a VeloPhex activity manifest. The Package Manager installs packages into the open project, writes project.json and project.lock.json, and restores the packages into the package cache. Activity packages in the offline feed# The installer includes an offline feed, shown as the Velophex Studio feed source, with the supported packages: Package Contents In new projects VeloPhex.System.Activities Core activities (logging, files, data, dialogs and more) and the Orchestrator activities (assets, credentials, queues, jobs, storage) Yes VeloPhex.UIAutomation.Activities Desktop and browser automation Install it yourself Velophex.Excel.Activities Workbooks and CSV Install it yourself (the Transactional Process template adds it) VeloPhex.UIAutomation.Core is also in the feed. It is a supporting library, not an activity package. See the Activity catalog for every activity. Open the Package Manager# On the Design ribbon tab, select Manage packages, or press Ctrl + P. In the Explorer, right-click Dependencies and select Manage packages…. In Project settings > Dependencies, select Manage packages…. The left side has Settings (the package sources), Project dependencies, All packages, and one entry per enabled source. Install a package# Select All packages, then the Browse tab. Search for the package, for example UIAutomation. Use the Package source list to search one source, and the filter menu for Include prerelease, Activity packages only or Compatible only. Select the package. The details show its signature, its source, its activities, dependencies, compatibility, and the capabilities it asks for (for example file system, network or browser access). Pick a Version and select Install. The change is added to a pending list; it is not applied yet. In the pending strip, select Review to see the project and dependency changes, then Apply. Discard drops the pending changes. Studio resolves all dependencies first, then writes project.json and project.lock.json, then restores. The new activities appear in the Activities panel. Consent for untrusted packagesIf a package is unsigned, comes from a source you have not marked as trusted, or asks for new host capabilities, the review asks for consent. Select I understand, install them anyway only if you trust the package. Capabilities tell you what a package intends to do; they are not a sandbox. If an install fails# Applying is all or nothing. If any package cannot be restored, Studio puts project.json and project.lock.json back exactly as they were and tells you The package changes were undone. The details are in Output on the Packages channel. Update or remove a package# Update one package: on All packages, open the Updates tab, select the package, pick the version and select Update. Then Apply. Update everything: select Update all (shown only when updates exist), then Apply. Remove a package: select it on the Installed tab and select Uninstall, then Apply. Or right-click it under Dependencies in the Explorer and select Remove dependency (direct dependencies only). Remove packages nothing uses: on the Design ribbon tab, select Remove unused > Remove unused dependencies. Studio lists what it will remove and asks you to confirm. Manage package sources# Studio comes with three sources, searched in this order: Source Location Trusted Velophex Studio feed The offline feed installed with Studio Yes My packages Documents\Velophex\Packages; Publish writes here by default No nuget.org https://api.nuget.org/v3/index.json No To add or change a source: Open Home > Tools > Package sources, or Settings in the Package Manager. Under Add a source, enter a name and the location (a folder, a share or a NuGet v3 feed URL), then select Add. To sign in to a private feed, select the source, enter User name and Password, and select Sign in. For your Orchestrator tenant feed, use a personal access token as the password. Select Trusted only for sources whose packages you trust. Use the up and down arrows to change the order, and the check box to turn a source on or off. Passwords are stored in Windows Credential Manager, never in Studio's settings files. Remove deletes a source and its stored sign-in. The Orchestrator tenant feed address is: TextCopyhttps://orchestrator.example.com/api/v1/tenants/<tenantId>/feed/v3/index.json Repair dependencies# The Dependencies node in the Explorer shows a package with a problem as: Status Meaning What to do Not resolved In project.json but not in the lock file Repair dependencies Not restored Not in the package cache, or a dependency is missing Repair dependencies, or enable the source that has it Could not be loaded In the cache but unusable, for example a broken manifest or an incompatible engine version Install a compatible version, or contact the package author To repair, right-click Dependencies and select Repair dependencies. Studio resolves the packages again and rewrites the lock file. The Package Manager's More menu also has Restore and Repair. Next steps# Use the new activities: Build workflows with activities. Build your own package: Build a custom activity package.

Activity packages in the offline feed

Open the Package Manager

Install a package

If an install fails

Update or remove a package

Manage package sources

Repair dependencies

Next steps