NetWiv documentation
이 콘텐츠는 아직 번역되지 않았습니다.
Guides and references for building applications with NetWiv and extending the framework. Public documentation is maintained in English.
Official website: netwiv.github.io.
Technical support classifications and validation results have the limits described in Support and validation. They do not establish service commitments or additional warranties; see license and support terms.
Build an application
Section titled “Build an application”| Guide | Topics |
|---|---|
| Deployment | Self-contained .NET, framework-dependent and optional NativeAOT publishing |
| Quickstart | Prepare packages, create a React app, run it and publish |
| Release bundles | Draft Releases, downloadable package feeds and checksums without NuGet.org publication |
| .NET compatibility | .NET 8 baseline, SDK/runtime 9 and 10, packages and validation limits |
| Linux | GTK/WebKit prerequisites, X11 and native Wayland, compositor and plugin limits |
| macOS | Mac prerequisites, main-thread startup, app/DMG bundles and signing limits |
| Project creation | CLI options, solution structure and development/build workflows |
| Frontend templates | Six choices and their toolchain requirements |
| React development | Development server, C# restarts and binding updates |
| Blazor Hybrid | Default managed desktop Razor hosting, experimental NativeAOT research and shared WebAssembly UI |
| Blazor Hybrid AOT future work | Deferred research, library fork alternatives and acceptance gates |
| Coding agents | netwiv mcp server for Claude Code, Codex, Cursor and other MCP agents |
APIs and security
Section titled “APIs and security”| Reference | Topics |
|---|---|
| C# SDK | Commands, state, events, ownership and lifecycle |
| Generic Host | Dependency injection, configuration, options, logging and hosted services |
| Frontend bindings | JS/TS generation and serialization support |
| Desktop frontend SDK | Single core/plugin entry point, desktop exclusions and migration from Tauri imports |
| Menus | Icons, menu items and About metadata |
| Plugin configuration | Settings, registration and capability permissions |
| Desktop plugins | Installation, contracts and feature-specific limits |
| Bundle resources | File staging and runtime paths |
| Custom URI protocols | Synchronous and asynchronous protocol handlers |
| Isolation and IPC | Isolation pattern, transports and validation |
| Remote URL patterns | URL matching for remote capabilities |
| Runners, versions and hooks | CLI configuration, version conversion and execution order |
Support and framework development
Section titled “Support and framework development”| Reference | Topics |
|---|---|
| Design principles | .NET usability and the NetWiv frontend contract |
| Support and validation | Platforms, distribution and unverified areas |
| API status | Implementation and comparison coverage for the pinned public API inventory |
| Platform behavior | Upstream constraints and deliberate C# differences |
| Native architecture | Responsibilities of .NET and Rust |
| C ABI | Memory, threads, callbacks and shutdown |
| Framework development | Source builds, tests and package creation |
| Upstream tests | Test inventory generation, ports and exclusion criteria |
Implementation and completed validation are different states. Read each feature’s platform limits together with its status; unverified behavior is not a compatibility pass.
Documentation conventions
Section titled “Documentation conventions”Public documents explain usage, contracts, design rationale and limits without requiring earlier conversations or a personal development environment. Examples identify required inputs and working directories. Validation instructions refer to repository tests and commands. Do not commit personal paths, work journals, per-run reports or execution logs, or add evidence collection to code or CI/CD. Unimplemented and unverified behavior must remain visible in public documents.
TAURI® is a trademark of The Tauri Programme within the Commons Conservancy.
NetWiv is an independent project. Its framework, plugins and templates are not affiliated with, endorsed by, or officially approved by The Tauri Programme within the Commons Conservancy.