VeloxDev.Core 6.0.1

<div align="center">

⚡ VeloxDev

Build modern, AI-controllable workflow editors on any .NET GUI — WPF, Avalonia, WinUI, MAUI, or WinForms.

🌐 Online Wiki

📁 Local Wiki

</div>

✨ What is VeloxDev?

VeloxDev gives .NET developers a complete foundation for building interactive workflow editors — the kind where users drag nodes, wire slots together, and watch data flow through a graph at runtime.

The workflow system is the core. Everything else exists to make workflows more extensible, more polished, and AI-controllable:

📦 Installation

Pick the adapter for your GUI framework and you get everything — workflow, agent, animations, and theming wired up for that platform.

Platform adapter packages (recommended)

Platform	Package	NuGet
WPF	VeloxDev.WPF
Avalonia	VeloxDev.Avalonia
WinUI	VeloxDev.WinUI
MAUI	VeloxDev.MAUI

Build a WPF workflow view suite with the CLI

Run these commands from an existing WPF project. Replace MyApp with the project's root namespace:

dotnet new install VeloxDev.WPF.Templates
dotnet add package VeloxDev.WPF

dotnet new wpf-v-slot -n SlotView -ns MyApp.Views -o Views
dotnet new wpf-v-node -n NodeView -ns MyApp.Views -o Views
dotnet new wpf-v-link -n LinkView -ns MyApp.Views -o Views
dotnet new wpf-v-selector -n TemplateSelector -ns MyApp.Views -o Views
dotnet new wpf-v-decorator -n GridDecorator -ns MyApp.Views -o Views
dotnet new wpf-v-minimap -n MinimapOverlay -ns MyApp.Views -o Views
dotnet new wpf-v-tree -n TreeView -ns MyApp.Views -o Views

dotnet build

The template package contains the Node, Slot, Link, Tree, template selector, grid decorator, and minimap overlay views. Each view template generates its files with the required VeloxDev workflow behaviors already connected.

The Avalonia, WPF, WinUI, and MAUI template suites expose the same style options. Common short aliases include:

All templates use -ns for the generated namespace.

Core-only packages (bring your own adapter)

Package	NuGet	Description
VeloxDev.Core		Workflow abstractions, MVVM generators, and runtime models — zero third-party dependencies
VeloxDev.Core.Extension		MAF-based Workflow Agent tools and additional runtime extensions

🚀 Quick Look

Define a node

// Declare a node — the Source Generator handles INotifyPropertyChanged,
// slot lifecycle, and command wiring automatically.
[WorkflowBuilder.Node<MyNodeHelper>]
public partial class MyNodeViewModel
{
    public MyNodeViewModel() => InitializeWorkflow();

    [AgentContext(AgentLanguages.English, "Input slot (receiver)")]
    [VeloxProperty] public partial MySlotViewModel InputSlot { get; set; }

    [AgentContext(AgentLanguages.English, "Output slot (sender)")]
    [VeloxProperty] public partial MySlotViewModel OutputSlot { get; set; }

    [AgentContext(AgentLanguages.English, "Display title shown in the node header")]
    [VeloxProperty] private string title = "My Node";
}

Let an AI control the workflow at runtime

// One fluent call wires up discovery, tools, and the agent session.
var scope = tree.AsAgentScope()
    .WithAutoDiscovery(assemblyName: "MyApp")
    .WithInteractionSafety(3)          // confirm before destructive ops; present choices via tool
    .WithSelectionHandler(ShowDialog)
    .WithConfirmationHandler(ShowDialog);

var agent = chatClient.AsAIAgent(
    instructions: scope.ProvideProgressiveContextPrompt(),
    tools: scope.ProvideTools());

The agent can then create nodes, wire slots, change routing credentials, and patch properties — all through natural-language instructions, with full undo/redo support.

Connect MCP servers for external tooling

// Load external tools via Model Context Protocol (stdio transport).
// Supports Node (npm install + node), Npx (npx -y), and Uvx (uvx) modes.
var mcpTools = await new McpScope()
    .WithMcpRoot(".evn/mcp")
    .LoadAsync(new[]
    {
        new McpServerConfiguration
        {
            Name = "Filesystem",
            RunMode = McpServerRunMode.Npx,
            NpmPackage = "@modelcontextprotocol/server-filesystem",
        },
        new McpServerConfiguration
        {
            Name = "Git",
            RunMode = McpServerRunMode.Npx,
            NpmPackage = "@modelcontextprotocol/server-git",
        },
    });

// Merge MCP tools into your workflow agent
var allTools = scope.ProvideTools().Concat(mcpTools).ToArray();

The McpScope handles npm package installation (idempotent, thread-safe) and stdio transport management automatically. Failed servers are reported via the ServerError event without blocking remaining servers.

🗂️ Repository Layout

VeloxDev/
├── Src/
│   ├── Core/
│   │   ├── VeloxDev.Core                   # Workflow abstractions, MVVM generators & runtime models
│   │   ├── VeloxDev.Core.Extension         # MAF-based Workflow Agent tools & runtime extensions
│   │   ├── VeloxDev.Core.Test              # Unit tests for VeloxDev.Core
│   │   └── VeloxDev.Core.Extension.Test    # Unit tests for VeloxDev.Core.Extension
│   ├── Adapters/
│   │   ├── VeloxDev.WPF                    # WPF platform adapter
│   │   ├── VeloxDev.Avalonia               # Avalonia platform adapter
│   │   ├── VeloxDev.WinUI                  # WinUI 3 platform adapter
│   │   ├── VeloxDev.MAUI                   # .NET MAUI platform adapter
│   │   └── VeloxDev.WinForms               # WinForms platform adapter
│   ├── Generators/
│   │   └── VeloxDev.Core.Generator         # Roslyn Source Generators (netstandard2.0)
│   └── Templates/                          # dotnet new item templates for GUI adapters
├── Examples/
│   ├── Workflow/      WPF · Avalonia · WinUI · WinForms · MAUI · Common(Lib)
│   ├── MVVM/          WPF · Avalonia
│   ├── Transition/    WPF · Avalonia · WinUI · WinForms · MAUI
│   ├── Theme/         WPF · Avalonia
│   ├── AOP/           WPF · Avalonia
│   ├── AOTReflection/
│   └── MonoBehaviour/ WPF
└── Docs/
    ├── VeloxDev.Docs           # Documentation site (Blazor WebAssembly)
    ├── VeloxDev.Docs.Browser   # Browser-hosted docs entry point
    └── VeloxDev.Docs.Desktop   # Desktop-hosted docs entry point

📄 License

Released under the MIT License. © 2025 Axvser