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:

https://xaml.io/s/Samples/Newtonsoft

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

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:

1. In the Solution Explorer, right-click the Dependencies node
2. Click “Add NuGet Package Reference…”
3. Search for a package and see the icon, description, download count, and version list
4. 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:

• Newtonsoft.Json
• CsvHelper
• AutoMapper
• FluentValidation
• YamlDotNet
• Mapster
• Humanizer
• AngleSharp

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.xaml and a StartupUri in App.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:

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.

Microsoft might finally give power users what they've been demanding: the ability to move the Windows 11 taskbar wherever they want. Plus, 3 major new chapters in Paul's next book, and a strange pick that solves his big issue with Windows Spotlight.

Windows 11

• Potentially good news for the 13 people who want to move the Taskbar to a different screen side
• Beta (but not Dev) with one new "feature"
• Release Preview for 24H2/25H2 with emoji 16.0, QMR improvements, network speed test, pan and tilt controls for compatible cameras, widgets improvements, more
• Lenovo revenues up 18% to $22.2 billion

AI/Dev

• Google announces 30-second audio generation
• Google sets a date for I/O 2026, but where in the Carmen Diego is Build 2026?
• Android 17 Beta is here with an even shorter runway
• With '26.3 out, Apple releases '26.4 Beta 1s

Xbox and gaming

• Phil Spencer is always in the spotlight, but he's been on the down-low for months
• Some hints for the future coming GDC 2026
• Kingdom Come Deliverance II, Witcher 3, more coming to Xbox Game Pass
• Avowed comes to the PlayStation 5 along with the Anniversary Update
• Microsoft is retiring user-created Xbox social clubs
• NVIDIA GeForce Now comes to Amazon Fire TV 4K Sticks

Tips & picks

• Tip of the week: Major progress on De-Enshittify Windows 11, the book
• App pick of the week: Bing Wallpaper
• RunAs Radio this week: Hacking using AI with Erica Burgess
• Brown liquor pick of the week: Lot 40 100% Pot Still Rye

Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell

Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly

Check out Paul's blog at thurrott.com

The Windows Weekly theme music is courtesy of Carl Franklin.

Join Club TWiT for Ad-Free Podcasts!
Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit

Lai-Ling Su: When Leadership Changes—Supporting Teams Through the Uncertainty

Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

"We have a once in a generational or once in a lifetime type of opportunity to fundamentally work with these leaders to shift the workplace environments and the workplace dynamics in the way that we've been trying to craft in the world of product and agile for the last few decades." - Lai-Ling Su

Lai-Ling brings a systems-level challenge that has profound implications for Scrum Masters everywhere. Australia is on the brink of its largest intergenerational wealth transfer in history—$3.5 trillion over the next couple of decades—with 70% of private and family businesses planning to sell or succeed as part of this generational change. 

This creates leadership vacuums as business leaders transition out and new ones step in. Some are family members stepping into roles without the full capability to lead; others are external CEOs facing resistance when they do things differently. 

These transitions stall decisions, lose customer confidence, and fracture once tight-knit teams. Lai-Ling sees this as an unprecedented opportunity for Scrum Masters to support both outgoing and incoming leaders through succession planning, capability uplift, and protecting teams during the transition. 

Teams need to be respected for what they've achieved, and Scrum Masters can serve as bridges—creating awareness about the team's strengths and facilitating dialogue between old and new leadership to ensure continuity.

Self-reflection Question: How might you proactively prepare your team to navigate an upcoming leadership transition, whether it's anticipated or unexpected?

[The Scrum Master Toolbox Podcast Recommends]

🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥

Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.

🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.

Buy Now on Amazon

[The Scrum Master Toolbox Podcast Recommends]

About Lai-Ling Su

Lai-Ling fixes the gap between operating model design and real-world delivery through her interim executive, consulting, capability building, and executive coaching work. She also equips product and transformation leaders with the capability everyone expects but no one teaches - how to navigate the people, politics, and performance expectations that come with their jobs.

You can link with Lai-Ling Su on LinkedIn.

Wes and Scott talk about the latest dev news: Node enabling Temporal by default, OpenAI acquiring OpenClaw, TypeScript 6, new TanStack and Deno releases, the explosion of AI agent platforms, and more.

Courtney Tolinski's Podcast

Phases: A Parenting Podcast https://phases.fm/

Show Notes

• 00:00 Welcome to Syntax!
• 01:11 Brought to you by Sentry.io
• 02:40 Node.js enables Temporal by default
  • Enable Temporal by default
• 04:08 OpenClaw acquired by OpenAI
  • OpenClaw, OpenAI and the future
• 09:36 Bots are taking over the internet
  • Wes’ tweet
• 15:30 TypeScript 6 Beta
  • Announcing TypeScript 6.0 Beta
• 17:00 TanStack Hotkeys for type-safe shortcuts
  • TanStack Hotkeys
• 18:05 Components will kill webpages
  • Components Will Kill Pages
• 19:39 Is Google Translate just an LLM?
  • Viridian’s tweet
• 23:29 Shaders.com
• 26:49 Voxtral Mini Realtime
  • Voxtral Realtime
  • Demo
• 29:51 Deno launches Sandboxes
  • Introducing Deno Sandbox
• 32:39 Oz by Warp.dev
• 38:10 Augment Code Intent
• 40:10 Sick Picks + Shameless Plugs

Sick Picks

• Scott: Samsung Remote
• Wes: Ice

Shameless Plugs

• Syntax YouTube Channel

Hit us up on Socials!

Syntax: X Instagram Tiktok LinkedIn Threads

Wes: X Instagram Tiktok LinkedIn Threads

Scott: X Instagram Tiktok LinkedIn Threads

Randy: X Instagram YouTube Threads

While working on a PR in Microsoft.Extensions.Logging I saw two variations of code and I wanted to check which one is faster. Not that it mattered in this piece of code, but every little counts and also, I like to explore random things.

Assume you have some numbers (zero-based) that represent predefined strings. And you want to convert those numbers.

In the previous post, you defined tenant templates directly against a project. In this post, you’ll create a project that includes a community step template.

Prerequisites

• An Octopus Cloud account. If you don’t have one, you can sign up for a free trial.
• The Octopus AI Assistant Chrome extension. You can install it from the Chrome Web Store.

Creating the project

Paste the following prompt into the Octopus AI Assistant and run it:

Create a Script project called "11. Script App with Community Step Template". 
Modify the deployment process to include the community step template with the website "https://library.octopus.com/step-templates/d166457a-1421-4731-b143-dd6766fb95d5" as the first step with the name "Calculate Deployment Mode".

This adds the community step template found in the Octopus community step template library as the first step in the deployment process. Community step templates use the URL as an ID to uniquely identify them.

Community step templates are contributed by the Octopus community and can be found in the Octopus Step Template Library. They provide additional functionality that you can easily add to your projects.

You can now create a release and deploy it to the first environment. The step will print the deployment details, indicating whether it is a new or a redeployment, and other helpful information.

What just happened?

You created a sample project with:

• A step sourced from the community step template library that calculates and prints deployment mode information.

What’s next?

The next step is to define project channels.