What problem does it solve?
Testing engine-level behavior across XNA-compatible runtimes normally requires setting up multiple local projects per backend and platform. XnaFiddle lets you author a small XNA-syntax project in the browser, run it immediately, and export it to a chosen runtime and platform — even linking against engine source instead of NuGet packages.
Core Features & Use Cases
- Cross-backend web fiddles: Write XNA-syntax code that compiles and runs directly in the browser without local project setup.
- Source-linked engine export: Export to MonoGame, KNI, or FNA targeting platforms like desktop, web, or Android, optionally linking engine source (emitting one .slnx with per-platform projects) so you can toggle engine build constants and prove engine-side behavior.
- Shareable upstream repros: Create public repros for KNI/MonoGame/FNA engine issues that maintainers can run in a couple of clicks.
- Gum and third-party library support: Fiddles are Gum-aware, and ILibraryPlugin implementations (e.g. KernSmithPlugin) auto-detect referenced libraries via IsUsedInSource and pull in the right NuGet packages at export.
- Use Case: You suspect a KNI rendering bug only appears with a specific build constant. Create a fiddle, export it source-linked to KNI for desktop, toggle the constant, and confirm the engine-side behavior — then share the public fiddle link with the KNI maintainers.
Quick Start
Ask the assistant to create an XnaFiddle that reproduces your engine behavior and export it source-linked to your chosen runtime and platform.