Set up your environment

Install the .NET SDK, make the VeloPhex SDK packages restorable, and install the activity package template.

You need a build machine that can restore the four SDK packages, and a Studio installation to try what you build. Prerequisites# The .NET 10 SDK. Activity packages target net10.0, or net10.0-windows when they use Windows APIs. Check with dotnet --list-sdks. A NuGet source that serves the VeloPhex SDK packages: Velophex.Workflow.Sdk and the VeloPhex.Platform.* packages it depends on, Velophex.Studio.Sdk, VeloPhex.ActivityPackage.Build and VeloPhex.ActivityPackage.Templates. Ask your VeloPhex contact which feed your release provides them on. nuget.org (or a mirror of it), for any third-party libraries your activities use. VeloPhex Studio, to install and run your package. See Install Studio. Any editor or IDE that builds .NET 10 projects. Make the SDK packages restorable# Add the VeloPhex feed to a nuget.config at the root of your repository, so every project and every build machine restores the same way: nuget.configXMLCopy<?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <add key="nuget.org" value="https://api.nuget.org/v3/index.json" /> <add key="velophex" value="https://packages.example.com/velophex/v3/index.json" /> </packageSources> </configuration> Replace the velophex value with the feed URL, or a local folder that holds the .nupkg files. If your organization uses NuGet package source mapping, map both spellings of the VeloPhex prefix to the VeloPhex feed. NuGet patterns are case-insensitive, so one pattern covers Velophex.* and VeloPhex.*: nuget.configXMLCopy<packageSourceMapping> <packageSource key="velophex"> <package pattern="VeloPhex.*" /> </packageSource> <packageSource key="nuget.org"> <package pattern="*" /> </packageSource> </packageSourceMapping> The VeloPhex prefixes are reservedPackage ids that start with VeloPhex. or Velophex. are VeloPhex's own. Studio and Robots refuse a package with such an id unless it carries the VeloPhex signature, so give your packages your own prefix, for example Contoso.Invoices.Activities. Install the template# PowerShellCopydotnet new install VeloPhex.ActivityPackage.Templates To install from a specific feed or a downloaded file instead: From a feedFrom a filePowerShellCopydotnet new install VeloPhex.ActivityPackage.Templates --add-source https://packages.example.com/velophex/v3/index.json PowerShellCopydotnet new install .\VeloPhex.ActivityPackage.Templates.<version>.nupkg Each template version pins one set of VeloPhex package versions (see Create an activity package). To get a newer set, install a newer template version: dotnet new install VeloPhex.ActivityPackage.Templates::<version>. Verify# PowerShellCopydotnet new list velophex You should see: TextCopyTemplate Name Short Name Language Tags ------------------------- ----------------- -------- --------------------------- VeloPhex activity package velophex-activity [C#] VeloPhex/Activities/Library Next steps# Create an activity package

Prerequisites

Make the SDK packages restorable

Install the template

Verify

Next steps