What if you could share a running .NET project with a link?
Not a code snippet in a blog post. Not a GitHub repo someone has to clone and build. A live, editable, runnable project. Open it in the browser, click Run, and it works.
Try it right now:
You’ll see a complete C#/XAML project referencing the Newtonsoft.Json NuGet package in a browser-based IDE. Click Run. The project compiles and executes entirely in your browser via WebAssembly. There is no server-side build step. Edit the code, change things, re-run. Your changes don’t touch the original.
XAML.io v0.6 makes this possible with two new features: NuGet packages in the browser and code sharing via URL.

New to XAML.io? XAML.io is a free, browser-based IDE for building .NET applications using C# and XAML. It includes a visual drag-and-drop XAML designer with 100+ controls, a code editor, and in-browser .NET compilation via WebAssembly. No installation, no signup required. It’s built by Userware and powered by the open-source OpenSilver framework. Try it →
Here’s how code sharing works.
Share Code: Create, Run, Share, Fork
Click the “Share Code” button, choose a name, and XAML.io generates a URL:
https://xaml.io/s/yourname/yourproject
Anyone with that link can:
- View the full source code in the XAML.io IDE
- Run the project with a single click
- Modify the code freely (their changes don’t affect your original)
- Fork the project to save their own copy to the Cloud (free account required)
No signup is needed to view and run shared projects.

Attribution is built in. When someone forks your project and re-shares it, the chain is preserved. If Project A is forked as B, and B is forked as C, someone viewing C sees “Forked from B” with a link, and following that shows “Forked from A.” Your work stays credited, no matter how many times it’s remixed.
Auto-run links. Append ?run=true to any shared URL and the app runs automatically when the recipient opens the link. They see the working app immediately, not just source code.
Think about the use cases
| Scenario | Before | With XAML.io v0.6 |
|---|---|---|
| Showing how a library works | Static code snippets in docs | Live, runnable project anyone can try |
| Teaching a concept | “Clone this repo and run it” | Share a link and the student opens and runs immediately |
| Sharing a prototype | Screenshots + zip file | Share a link and the stakeholder sees it running live |
| Answering a question | Paste code into Slack | Share a link that the other person can actually run |
NuGet Packages in the Browser
Until v0.6, XAML.io projects could only use the built-in .NET libraries and OpenSilver’s UI controls. Now you can add any compatible NuGet package, with a workflow that should feel familiar:
- In the Solution Explorer, right-click the Dependencies node
- Click “Add NuGet Package Reference…”
- Search for a package and see the icon, description, download count, and version list
- Select a version and click Add

The package is immediately available in your C# and XAML code. See it in action: the Newtonsoft.Json sample shows a NuGet package, C# code-behind, and a XAML UI all running together in the browser.
What packages work?
Non-UI .NET libraries: Anything targeting .NET Standard 2.0/2.1 or .NET 5-10 that works with Blazor WebAssembly. This covers the vast majority of popular packages: JSON processing, CSV handling, HTTP clients, validation, data transformation, and more.
OpenSilver-compatible UI libraries: NuGet packages built for or compatible with OpenSilver, usable in both C# code and XAML markup.
If a package relies on APIs unavailable in WebAssembly (direct file system access, certain networking APIs), it won’t work. Most non-UI libraries are fine.
Interactive samples: try them now
We’ve published official sample projects for popular .NET libraries. Each one is a complete, runnable solution with the NuGet package already referenced. Click any link and the app will compile and run automatically:
Fork any of them to start your own project. We’ll be adding more over time.
For Library Authors
If you maintain a .NET library, you can create a live, interactive demo on XAML.io and share it with a single URL. Go to xaml.io, add your NuGet package, write a small demo, sign in (free), and click “Share Code”. Link to it from your README, docs, or NuGet page.
If you create a sample, share it on the XAML.io Forums or let us know. We’d love to feature community-created samples.
Also in v0.6
NuGet and code sharing are the headlines, but this release also includes improvements shipped over recent months:
- XAML Autocompletion (IntelliSense): Context-aware suggestions for elements, attributes, and property values while editing XAML.
- “Fix with AI” button: Appears next to XAML compilation errors. One click triggers an AI-powered fix attempt.
- WPF-style default template: New projects start with
MainWindow.xamland aStartupUriinApp.xaml, matching the default structure of WPF applications. - Improved mobile support: View shared projects, make quick edits, and run code on a phone or tablet. Desktop browsers remain recommended for extended sessions.
- Error squiggles: Compilation errors are underlined directly in the source code.
- Split editor view: Split the workspace vertically or horizontally (e.g. XAML on the left with the designer on the right)
- Community forums: The new XAML.io Forums are live. Ask questions, share what you’ve built, and connect with other XAML.io users.

Under the Hood: Client-Side Compilation, No Lock-In
XAML.io compiles and runs .NET code entirely in the browser. The C# compiler itself runs in your browser tab, using the same .NET WebAssembly runtime that powers Blazor WebAssembly applications. When you click Run, your code is compiled locally. Nothing is sent to a server. There is no round-trip, no cold start, and no build queue.
The UI layer uses XAML with the same syntax as WPF, and OpenSilver renders it as real DOM elements rather than drawing to a canvas. A TextBox becomes an actual <textarea>, an Image becomes an <img>, a MediaElement becomes a <video>, a Path becomes an <svg>. Open your browser’s DevTools on a running XAML.io app and you’ll see a real DOM tree, not a single <canvas> element. The compiled output is a set of static files (.wasm, .js, index.html) that can be hosted on any web server or CDN.
You’re not locked in. Every project can be downloaded as a standard Visual Studio solution and continued in Visual Studio, VS Code, or any .NET IDE. The underlying framework (OpenSilver) is fully open-source. XAML.io is a frictionless starting point, not a walled garden.
Getting Started
1. Explore a sample (no signup needed)
Open any of the interactive samples above. Click Run, edit the code, see the results.
2. Create your own project
Go to xaml.io. A new project loads instantly. Build your UI three ways: drag controls from the toolbox, write XAML by hand (now with IntelliSense), or describe what you want and let the AI assistant generate it.
3. Share your work
Sign in with your Microsoft Account (free). Click “Share Code” to get a URL. Send it to anyone.
4. Download for Visual Studio
Click the download button to get a .zip containing a standard Visual Studio solution. No lock-in.
Limitations and What’s Next
XAML.io is a tech preview. We want to be upfront about what doesn’t work yet:
- Not a desktop IDE replacement: XAML.io is designed as a companion to Visual Studio, not a substitute. Features like debugging, refactoring, and advanced project tooling are best handled in a desktop IDE. Think of XAML.io as the fastest way to prototype, share, and learn.
- One project per solution: multi-project solutions are planned
- NuGet compatibility: packages that rely on APIs unavailable in WebAssembly won’t work (most non-UI libraries are fine)
- Desktop recommended: mobile works, but the full experience is best on a desktop browser
We’re actively improving the product. Suggest features or vote on others’ ideas at feedback.xaml.io, ask questions on the forums, or contact us directly.
Here’s what’s coming next:
| Feature | Description |
|---|---|
| Improved WPF compatibility | Broader support for WPF APIs and patterns |
| Multi-project solutions | Class libraries, shared projects, multiple entry points |
| One-click deployment | Publish running apps online: share a live app, not just source code |
| VB.NET and F# support | Expanding language options beyond C# |
| Improved performance | Faster compilation, snappier interactions |
Everything you build on XAML.io is yours. Download it, open it in Visual Studio, deploy it wherever you want. The underlying framework is fully open-source. There is no lock-in.
Now you can share running .NET code with a link. Try it. Build something. Share it. See what happens when someone clicks your link and your code just… runs.
Questions? Feedback? Join the XAML.io Forums, reach out on X/Twitter (@xaml_io), or contact us directly. If you’re exploring migrating a WPF or Silverlight application to the web, our team can help with that too.
xaml.io | Free. No install. No signup required.