Services for a working application.
Look up the BASIC contract, then follow a complete workflow. A public CLR helper is not automatically a BASIC API.
Application, paths and preferences
Keep distributable resources separate from writable user state. Settings is a scalar preference store, not a credential vault.
Signatures & behaviorFile and Path
File operations use strict UTF-8 or byte arrays. Output directories must exist; the application bundle is read-only.
Signatures & behaviorDialogs, clipboard and platform
Native interactions can be cancelled or denied. Check returned values before doing the next operation.
Signatures & behaviorHTTP and downloads
Separate transport failure, HTTP status and response-body validation. Async functions require Await from an Async procedure.
Signatures & behaviorStructured JSON
JsonValue represents a JSON document or subtree; Json.Value extracts a scalar.
Signatures & behaviorSQLite connections, commands and transactions
Own the database lifetime, apply migrations first and use parameterized commands for entered values.
Signatures & behaviorRecords and data binding
A loaded result, an editable draft and committed database state are different things.
Signatures & behaviorCollections, trees and drag payloads
Read the indexing and ownership rules instead of assuming every collection works like an array.
Signatures & behaviorReports
Choose a declared report resource or an explicit recordset, then select the output action.
Signatures & behaviorErrors and assertions
Use structured errors to preserve cleanup, and assertions to record behavior that must remain true.
Signatures & behaviorDeveloper CLI
Project, package and local distribution commands.
Command reference20f4bfed6b · Build manifest