Skip to content

.NET reference for workspace C#

Moltaro publishes a curated .NET reference for the C# surface supported inside the workspace Net Operation Project. It is documentation, not an assembly download and not the broader NetPackage surface.

The exact contract of an installation is available from:

GET ${WORKSPACE_API_BASE_URL}/api/workspace/admin/net-operation-project/developer-surface

WORKSPACE_API_BASE_URL is the API host recorded in the downloaded workspace-specific agent guide. This endpoint is not served by moltaro.com; see Connect to a workspace API.

That response lists supported assembly versions and every supported constructor-injected type, including its purpose, lifetime, module key, ServiceKind, preferred status, supported function contracts, transaction semantics, and documentation URL. It also confirms that the current generated workspace contract is automatically present in language-service and build snapshots.

The XML files use the standard C# compiler documentation format. Agents can join a <member name="..."> entry to a symbol returned by completions, hover, or signature help. The manifest checksum lets tooling detect a changed reference without downloading all XML files.

The reference includes function and data-source contracts, supported core services, dynamic-entity runtime services, preferred Boards, Entitlement, and Work Schedule application-automation services, their advanced direct-DB counterparts, Currency Rates cached lookup, and the request/result/enum types needed by those contracts. Application automation is the recommended Net Operation Project surface and is marked ApplicationAutomation; lower-level package services are marked TrustedDirectDb. The FP-01 File Protection status facade is read-only and is available to API-hosted Action, Command, and HttpEndpoint functions; Worker-hosted Job and TriggerHandler functions are not advertised until File Protection is registered in Worker.

It excludes package identity, package-owned schema authoring, model-building, manifests, migrations, install lifecycle, and host-only orchestration services. Public CLR visibility is not a support promise; use developer-surface as the authoritative allow-list.