Skip to content

Releases: builtbybel/FluentTweaker

FluentTweaker - Dawn of the Fluent Era

Choose a tag to compare

@Belim Belim released this 06 Jun 18:10
78be877

Winslopr grows up: meet FluentTweaker

Background

Winslopr was my first real experiment with WinUI 3. Since then I've grown a lot more confident with the framework, and that shows in how FluentTweaker is built.

So I've decided to retire Winslopr and move forward with FluentTweaker as its successor, a cleaner, more capable app built as part of the Fluent ecosystem alongside FluentCleaner.

Over the years I've released a number of Windows 10/11 optimizers and debloaters as C# WinForms / .NET apps. The best ideas and features from those tools are gradually making their way into FluentTweaker. Now that I've grown comfortable with WinUI 3, it feels like the right home for all of it, one modern, native app instead of a scattered collection of old projects.

The timing feels right too. Microsoft appears to be moving away from web app slop and refocusing on WinUI and native app development, which gives me a lot more confidence that I'm building on the right foundation and a lot less worry about waking up one morning to find the framework abandoned

Maintaining two apps that do the same thing doesn't make sense. FluentTweaker does everything Winslopr did and much more and it fits cleanly into the same workflow if you already use FluentCleaner.

FTweaker.mp4

What FluentTweaker brings:

βœ… WinUI 3 Native Windows 11 look, Mica backdrop, proper dark/light mode. if you already use FluentCleanerfor cleaning and maintenance, FluentTweaker slots in as the tweaking and optimization layer. Same architecture, same INI-based database model, same WinUI 3 native feel.
βœ… Transparent & safe All tweaks are stored in a plain Wintweak2.ini;readable, editable, no black-box scripts. Same approach as FluentCleaner's Winappx2.ini.
βœ… Winget integration Install, uninstall and upgrade apps directly
βœ… AppX debloater Remove pre-installed bloatware with a clean checklist UI
βœ… Custom tweaks Write your own PowerShell scripts or INI-based registry tweaks
βœ… Actively developed Same cadence as FluentCleaner, same architecture
βœ… Community Store an open, pull-request-driven package index. Anyone can contribute a tweak, script or database update. Transparent by design

Store

The built-in Store lets you browse and install community-contributed packages directly inside the app.
Packages live in the Store folder of this repository, a simple JSON index plus the files themselves.


Thanks to everyone who used and starred Winslopr, same place, new name. πŸ™

Winslopr 26.04.04

Choose a tag to compare

@Belim Belim released this 06 Apr 17:11
908a713

Warning

Unofficial domain notice: I do not own or operate winslop.com and I'm not affiliated with whoever registered it.
Even if it currently redirects to this GitHub repo, a third-party domain can be changed at any time (phishing, fake releases, malware links).
My only official pages are on GitHub: github.com/builtbybel/ (repo + releases).
Download Winslop only from GitHub Releases.

+++ Winslop is now Winslopr: short for Windows Slop Remover. Same tool, clearer name +++

  • [New] Unified Plugins & Scripts management: Plugins and Tool Scripts are now managed in a single dialog (PluginsDialog) instead of two separate places (Plugins and Scripts/Extensions). Routing is based on the manifest type= field: type=tool --> Scripts/ folder, Default --> Plugins/ Folder
  • [Improved] Reduced unnecessary resource usage and made the app feel smoother in daily use, which is saying something given that WinUI 3 still behaves like a small monster now and then
  • [Fix;Critical] Fix winget source agreements on fresh Windows installs. winget list and winget upgrade now run with --accept-source-agreements --disable-interactivity, so the Install tab works out of the box without needing a prior manual winget interaction in the terminal #77
  • [Improved] UI has been refined across the app to feel lighter, cleaner, and more modern
  • [Added] "Plugins" entry to the settings flyout which opens Plugins dialog directly
  • [Improved] Per-entry folder-aware installed state detection via File.Exists(targetDir + fileName). This fixes false positives where same-named files in different folders were incorrectly shown as installed
  • [Removed] ThirdPartyDetector as third-party tools are now discoverable and installable directly via the Plugins dialog
  • [Removed] Share feature from the settings dropdown (redundant)
  • [Removed] Cleaned up obsolete Localization keys: Settings_ToolScripts, Settings_OpenToolsPage, MenuShare
  • [Updated] Localization es-ES; zh-CN
Winslopr-26.04.04.mp4

Release package:
Winslop-26.04.04.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.

Winslopr 26.04.02

Choose a tag to compare

@Belim Belim released this 03 Apr 09:08
295c6c0

Warning

Unofficial domain notice: I do not own or operate winslop.com and I'm not affiliated with whoever registered it.
Even if it currently redirects to this GitHub repo, a third-party domain can be changed at any time (phishing, fake releases, malware links).
My only official pages are on GitHub: github.com/builtbybel/ (repo + releases).
Download Winslop only from GitHub Releases.

+++ Winslop is now Winslopr: short for Windows Slop Remover. Same tool, clearer name +++

Shoutout to everyone who said WinUI 3 is "for the visually impaired" πŸ˜†

  • [NEW] Compact Spacing Mode. Because WinUI 3 has a talent for turning pixels into margins, Winslopr now brings back a denser, more compact layout, especially nice for users coming from the old WinForms version. Same modern WinUI 3 base, less UI bloat
  • [New] Friendly Tools Detection Winslopr now checks your Plugins / Scripts folders on startup and greets any familiar faces, W11Debloat, Chris Titus WinUtil, and more. They play well together. Winslopr doesn't try to do everything. For the gaps, these tools have your back
  • [Improved] Works best on Windows 11 25H2 Verified and tested. Older builds still work, but 25H2 is where it shines
  • [Fix] Icons missing on Windows 10 Segoe Fluent Icons is a Windows 11 exclusive. On Windows 10 all icons showed up as empty boxes, not great. Fixed with a proper font fallback to Segoe MDL2 Assets #75
  • [Improved] Cleaner UI layout Toolbar controls (filters, profile picker) are now inside the content Card where they belong
  • [Added] Turkish language support tr-TR is now part of the family. Settings > Language.
explorer_LucspAZSkG

Release package:
Winslop-26.04.02.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.

Winslopr - 26.03.230

Choose a tag to compare

@Belim Belim released this 30 Mar 18:53

Warning

Unofficial domain notice: I do not own or operate winslop.com and I'm not affiliated with whoever registered it.
Even if it currently redirects to this GitHub repo, a third-party domain can be changed at any time (phishing, fake releases, malware links).
My only official pages are on GitHub: github.com/builtbybel/ (repo + releases).
Download Winslop only from GitHub Releases.

+++ Winslop is now Winslopr: short for Windows Slop Remover. Same tool, clearer name +++

  • [New] Windows 11 25H2 (Build 26200) support verified
  • [New] Fresh app icon with a cleaner, more on-brand look
explorer_FMH1cPiOtM
  • [New] Close (X) button on the Settings panel
  • [New] Pairs well with tools like Chris Titus Tech, W11Debloat or Microsoft PC Manager. If a feature isn't in Winslopr yet, chances are it's already available as a plugin or script. Focused scope by design. Winslopr does less on purpose, so it fits into any existing setup
  • [Improved] Undo and restore is more reliable
  • [Improved] Replaced the Settings SplitView pane with a simpler right-side overlay panel
  • [Improved] Settings panel no longer causes the app layout to shift or clip controls when opening, resizing or moving the window
  • [Improved] Settings panel has its own glass look
  • [Improved] Filter chips and action buttons share one toolbar row on every page
  • [Improved] Reduced resize-related UI glitches that could cause controls and inner cards to get clipped.
  • [Improved] Search bar is more compact
  • [Improved] Debloater in the Apps page with better bloatware detection and faster scan
  • [Improved] Reduced memory usage and smaller executable size
  • [Improved] Better support for external scripts including W11Debloater and similar tools
  • [FIX] Actions menu button no longer gets cut off on narrow windows
  • [FIX] Status messages and extension count no longer overwrite each other in the Tools page
  • [Updated] Translation es_ES #73
  • [Updated] Translation zh-CN #68
  • [Added] Translation Portuguese (Brazil) #67
Winslopr_ctTNb2dlc4 ---

Release package:
Winslop-26.03.230.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.

Winslopr - The Rename Drop

Choose a tag to compare

@Belim Belim released this 28 Mar 20:47
ebfca65

Warning

Unofficial domain notice: I do not own or operate winslop.com and I'm not affiliated with whoever registered it.
Even if it currently redirects to this GitHub repo, a third-party domain can be changed at any time (phishing, fake releases, malware links).
My only official pages are on GitHub: github.com/builtbybel/ (repo + releases).
Download Winslop only from GitHub Releases.

+++ Winslop is becoming Winslopr (Windows Slop Remover) +++

Yes, a letter is missing. No, it's not a typo.

"Winslop" was always a play on words: Windows + Slop. The idea was simple: Windows is full of junk, and this app cleans it up. That worked, until the internet had the same idea and started calling Windows itself "Winslop." Fair point, but inconvenient

And honestly, can you blame them? Between forced Copilot integrations, ads in the Start menu, Recall, and an update cadence that sometimes feels like Microsoft is stress-testing how much nonsense users are willing to tolerate, Windows has never felt sloppier.
We're debloating faster than they're bloating. It's a race we never signed up for. To be fair, Microsoft has started to dial some of this back recently, which at least shows they know things got out of hand

Search "Winslop" today and you'll find thousands of frustrated posts, memes, and rants about Windows and somewhere buried at the bottom, almost invisible, the app that actually tries to fix the problem.

So it had to happen. Not because the old name was bad, but because it stopped being specific enough. The internet stole it 😭 The perfect name doesnt matter if you dont own it anymore

Winslopr felt like the obvious fix. Close enough to the original to still be recognizable, but distinct enough to stand on its own.

And now it actually means something: Windows Slop Remover. It says what the app does, the mission is still the same, and it still sounds like a proper name. Not the object, the actor. Not the slop itself, the thing removing it.

Flickr dropped an e. Tumblr too. Winslopr drops one as well. No big adjustment needed. It's the same Winslop. Same mission. Just with a name that finally belongs to the app instead of the problem.


This is the first release under the new name.

The GitHub repository will also be renamed to Winslopr soon.

Why the rename?
  • Winslopr actually means something
    It now stands for Windows Slop Remover. That makes the name a lot more direct.
  • It's easier to find
    Winslop ended up becoming a general nickname for Windows itself, which made the app harder to search for. Winslopr fixes that.
  • It still feels familiar
    I didn’t want to throw the old name away completely. Winslopr keeps the original vibe, just in a more distinct form
  • **And yeah, I hope you dont hate me for dropping one letter πŸ˜„ **
    Same app, same mission. Just a name that finally belongs to the tool
Same.slop.killer.new.identity.mp4

If you're interested in some of the background behind this release, including the move from WinForms to WinUI 3, you can read more here and #36

Winslop 26.03.211

Choose a tag to compare

@Belim Belim released this 26 Mar 22:22
9202f5c

New WinUI3: Cleaner. Faster. More focused.

After two weeks with WinUI 3, I guess it's safe to say… we're getting along now. Winslop has moved from WinForms to WinUI 3 and this update is the result: a fully reworked interface built around one idea, staying out of your way

The old sidebar is gone, replaced by bottom navigation that keeps the focus on content. Pages open instantly, without unnecessary transitions. Search is right where you expect it, and settings are always within reach in the title bar.

Status indicators make it easier to see what needs attention at a glance. Action buttons, Inspect, Apply, Restore are more compact, more consistent, and adapt to your system accent color. Even the Actions menu has been toned down, so it no longer competes with the rest of the interface

Everything is theme-aware. Switch between light and dark mode inside the app, and dialogs, buttons, and controls update with it, no App restart needed.

Winslop still does exactly what it always did. It just finally looks the part

Take a look for yourself in the short intro video below.

With the transition from WinForms to WinUI 3, the app has a completely new face. New design language, new architecture, new vibe. So I'm asking myself, does the name still fit?

I want to hear from you:

Does "Winslop" still work for you, or does it feel generic?
Should the new UI chapter come with a new identity?
Got a name idea that's short, memorable and doesn't sound like every other "Win-something" tool?

Drop it here in the comments. If there's enough momentum, we'll make it official.

-Belim

winslop200.mp4

Release package:
Winslop-26.03.1201.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.

Winslop 26.03.155

Choose a tag to compare

@Belim Belim released this 25 Mar 12:27
c60b7db

Previously built on WinForms now fully rewritten in WinUI 3 (.NET 10).

Winslop was always meant to be a bit self-ironic - "sloppy Windows tweaking" and honestly, it stuck. But lately something funny is happening: users keep emailing me saying they can't tell Winslop apart from Windows itself anymore. "I just winsloped my PC" has become a thing apparently.

With the transition from WinForms to WinUI 3, the app has a completely new face. New design language, new architecture, new vibe. So I'm asking myself, does the name still fit?

I want to hear from you:

Does "Winslop" still work for you, or does it feel generic?
Should the new UI chapter come with a new identity?
Got a name idea that's short, memorable and doesn't sound like every other "Win-something" tool?

Drop it here in the comments. If there's enough momentum, we'll make it official.

-Belim

What's New

Winslop_FfhsrCRtys
  • [NEW] Search is now hidden by default. Just click the magnifying glass in the title bar to show it whenever you need it
  • [NEW] Support menu: share Winslop with friends via the native Windows share dialog as it opens straight from the Support button in the sidebar
  • [IMPROVED] Settings page got a fresh look with cleaner, wider cards
  • [IMPROVED] Extensions section now shows Plugins, Tools and Winslop Legacy as separate entries with quick-launch buttons
  • [IMPROVED] Quick access to Winslop Legacy added to launch the classic version straight from Settings
  • [IMPROVED] App info and compatibility details are now neatly tucked away under the About section
  • [FIXED] Scrollbar in Settings no longer covered part of the content
  • [FIXED, CRITICAL] App installs from the Install page were sometimes interrupted by a winget prompt. Added --source winget to prevent multi-source conflict prompt during install and upgrade
  • [IMPROVED] First-time notice about the WinUI 3 rebuild is now a small banner you can dismiss, so no more popup
  • [IMPROVED] Internal app folders renamed for consistency, there is no user action needed
  • [ADDED] Add zh-TW (Traditional Chinese, Taiwan) translation for WinUI 3
  • [UPDATED] Updated localization and support for Chinese, French, Spanish, and Russian

Release package:
Winslop-26.03.155.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.

Winslop 26.03.140

Choose a tag to compare

@Belim Belim released this 20 Mar 17:23
b487845

Note

What annoys you most about Windows 11?

59 community-sourced annoyances filterable, with fixes.
See what Winslop handles and what needs extra tools.

Previously built on WinForms now fully rewritten in WinUI 3 (.NET 10).

This release is a pretty hard break from the old Winslop WinForms / .NET Framework legacy build.

Winslop just got faster and more stable.
This release focuses entirely on what matters most fixing critical bugs and making the app feel snappier. No new features, just a cleaner, more reliable experience. The update is highly recommended as it resolves several issues that could cause unexpected crashes during normal use

What's New

Fixes

  • [CRITICAL] Fixed a crash that occurred after running an inspection and then toggling "Show misconfigured only"
  • [FIX] Logger now always scrolls to the bottom after an inspection, so no more manual scrolling
  • [FIX] App language setting was not reflected in the language selector on the Settings page. It now correctly pre-selects the active language
  • [FIX] Apps page list items now highlight on hover

Improvements

  • [PERF] App starts faster as feature loading begins in the background before the window appears
  • [PERF] Filtering the feature list is noticeably snappier
  • [UI] Tools page redesigned: primary action button now uses accent style, placeholder shown when no tool is selected, help hint via info bar
  • [UI] Tool icons replaced with colorful emoji so it works on Windows 10 and 11
  • [UX] Uninstall action now asks for confirmation before proceeding
  • [UI] Cleaner look: removed the grey card border inside the content area, added a subtle shadow for depth
  • [UI] Separator between the feature tree and log area is now properly styled
  • [UI] Apps page: replaced "Scanning..." checkbox placeholder with a proper loading spinner
  • [UI] Plugin dialog buttons split into two rows, so no more clipped/missing buttons
  • [NEW! ADDED] Added Raphire's Win11Debloat to plugins https://github.com/Raphire/Win11Debloat (Not included by default, needs to be installed via Settings > Extensions > Plugins)
  • [UPDATE] Improved Windows Update Tamer Script/Extension in Tools page
  • [ADDED] Spanish language support, Thanks to Javier Melio
  • [ADDED] Hungarian language support, Thanks to John Fowler
  • [Updated] Chinese language support

Release package:
Winslop-26.03.140.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.
The program folder now also includes Winslop.Legacy.exe if you still want to enjoy the classic version

Winslop 26.03.130

Choose a tag to compare

@Belim Belim released this 18 Mar 10:50
788b064

Note

What annoys you most about Windows 11?

59 community-sourced annoyances filterable, with fixes.
See what Winslop handles and what needs extra tools.

Previously built on WinForms now fully rewritten in WinUI 3 (.NET 10).

This release is a pretty hard break from the old Winslop WinForms / .NET Framework legacy build.

This wasnt a lazy port, a paint job, or one of those "internally modernized" updates nobody notices. Around 50% of the codebase was rewritten from scratch. Because apparently I enjoy making my life harder. Genius move πŸ€¦β€β™‚οΈ

What's New

Added

  • Compatibility check: Settings now shows whether your Windows version is fully compatible with Winslop (βœ… for Windows 11, ⚠️ for Windows 10)
  • Theme switcher: Choose between System, Light, or Dark mode (requires restart)
  • Backdrop switcher: Switch between Mica and Mica Alt live in Settings
  • Russian and Chinese language support

Improved

  • Improved German language support
  • Log Inspector redesigned with dark theme matching the app's WinUI 3 aesthetic
  • Update page modernized with clean Fluent Light design
  • Settings page reorganized with collapsible sections (Extensions, Compatibility)
  • Removed duplicate Import/Export from the toolbar menu (already in profile selector)

Fixed

  • ScrollViewer on Settings page now scrolls to the bottom correctly
  • Title bar button colors now match the selected theme on restart
Winslop_Qc3TtX2RDk

Release package:
Winslop-26.03.130.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.
The program folder now also includes Winslop.Legacy.exe if you still want to enjoy the classic version

Winslop - Final WinUI3 Release

Choose a tag to compare

@Belim Belim released this 15 Mar 16:49

Previously built on WinForms now fully rewritten in WinUI 3 (.NET 10).

This release is a pretty hard break from the old Winslop WinForms / .NET Framework legacy build.

This wasnt a lazy port, a paint job, or one of those "internally modernized" updates nobody notices. Around 50% of the codebase was rewritten from scratch. Because apparently I enjoy making my life harder. Genius move πŸ€¦β€β™‚οΈ

πŸš€ Winslop – WinUI3 Final release

"I told myself I'd stop after 4–5 releases. That turned out to be absolute nonsense"

Winslop_T6K1KAjABb

So yeah, here we are: the final WinUI 3 release of Winslop.

If you've been following the project, you already know the pattern.
If youre new here: welcome to probably the most unnecessarily overengineered Windows tweaker on GitHub πŸ˜„

Release III was the point where I finally felt like I understood WinUI 3.
Release IV is where I actually managed to do something useful with that knowledge. And now I've got something that genuinely works pretty well. Whether I personally like it yet is another story. I'll probably need a little more time to get used to it

As for the legacy Winslop version, I wrote more about that here: #36 (comment)
That version isnt dead. It'll still get new feature toggles here and there
But as things stand right now, it probably wont get the bigger stuff that made it into this branch, like localization, dark mode, and other actually modern features. At some point I have to go along with where Windows is heading, otherwise I'll just get left behind.
You guys probably know the feeling.

The community poll is still ongoing, and right now the modern version is slightly ahead with 51% vs 48%.

I'm keeping the poll open because I’m genuinely curious to see whether that 48% will shift over time and maybe, under the right circumstances, end up giving the modern version a chance after all.

The Microsoft emails are still coming in.
And I did rewrite about half the app, so make of that what you will.

πŸ—³ Haven't voted yet? There's still time:
Join the poll

Whats new?

Not everything made it into this listm, mostly because I lost track

Added

  • Full app localization with support for English, German, and French
    For translators: LOCALIZATION.md
  • Keyboard shortcuts for all major menu actions:
    • Ctrl+T – Toggle All
    • Ctrl+Z – Undo last changes
    • F5 – Refresh
    • Ctrl+L – Copy log to clipboard
    • Delete – Clear log
  • Zoom support for the Home page > Feature tree (Ctrl+Scroll). So WinUI 3 controls carry significantly more padding and spacing than their WinForms equivalents; a ZoomMode was added as a practical workaround to let users reclaim vertical space on smaller screens
  • Language-independent profile matching for feature tree selections
  • Built-in AI Panic Mode profile for quickly disabling Windows AI-related features
  • WINSLOP_SELECTION_V2 Changed the selection export format and added a stable profile selection format based on internal feature IDs and plugin file IDs
  • Reworked Settings page with centralized extension management
  • Context menu on right-click for individual tree nodes: Analyze, Fix, Restore, Help
  • Plugin analysis now included in the combined analysis summary dialog
  • Combined analysis summary after full inspection showing native features and plugins separately:
    • Windows Features : X of Y OK
    • Plugins : X of Y OK
    • Total : X of Y OK
  • Hyperlink to Online Log Inspector directly in the analysis result dialog
  • "No plugins selected" message in log when plugin analysis is skipped
  • Profile ComboBox with built-in Export, Import, and "Open profiles folder" actions
  • [CRITICAL] Search filter respects IsVisible state, so context menu actions (Analyze/Fix/Restore) now correctly skip hidden nodes
  • Log output now color-coded by severity using RichTextBlock and not TextBox
    • πŸ”΄ Red – Errors
    • 🟠 Orange – Warnings
    • Gray – Info (theme-sensitive via TextFillColorPrimaryBrush)
  • Nav highlight auto-refreshes on Windows light/dark theme switch
  • Per-page menu state: Export, Import, Undo, Manage Plugins disabled on non-Features pages
  • More options flyout button (β‹―) replaces separate Toggle/Undo/Refresh buttons and old log actions ComboBox
  • Log actions submenu under More options: Inspect online, Copy, Clear, Log checked/unchecked/summary
  • Plugin counters (TotalChecked, IssuesFound) added to PluginManager so it mirrors FeatureNodeManager
  • [CRITICAL] UnhandledException + TaskScheduler.UnobservedTaskException handlers to prevent silent crashes

Improved

  • Analysis summary moved to end of log (after dialog closes) so auto-scroll always lands at the bottom
  • More options menu replaces three separate icon buttons. Should bring a cleaner toolbar, less visual noise
  • LogActionsController removed and actions are now wired directly as MenuFlyoutItem handlers, no ComboBox dependency
  • Nav buttons theme-aware highlight via NavigationService.UpdateHighlight() so it reacts to live theme changes
  • ApplyFilter now iterates item.Children.ToList() snapshot to prevent collection-modified crashes
  • ApplySearch guards against _rootItems == null during page initialization
  • Analysis dialog now uses a StackPanel content with a HyperlinkButton instead of plain string
  • Improved profile import/export so selections no longer depend on localized feature or category names
  • Improved plugin profile handling by using the plugin script filename as a stable identifier
  • Improved extension discoverability by separating native Feature Tree plugins from tool scripts in Settings
  • Improved accessibility for international users with a fully localized UI across three languages
  • Changed the Settings page structure to manage extensions in a more native and unified way

Removed

  • Log actions ComboBox (comboLogActions) is eplaced by flyout submenu
  • LogActionsController class is no longer needed
  • Separate Toggle All / Undo / Refresh buttons is consolidated into More options flyout
  • Intermediate analysis dialog shown before plugin analysis are replaced by single combined dialog after both complete
  • Removed support for the old path/name-based selection format

Fixed

  • Context menu Analyze/Fix/Restore now respects active search filter (IsVisible check added to AnalyzeFeature, FixFeature, RestoreFeature)
  • Plugin nodes correctly skipped during native feature analysis and vice versa
  • Summary log entry no longer appears before plugin results

Migration note

WinForms allowed direct, compact tree manipulation via TreeNode.ForeColor, NodeFont, and AfterCheck –
all handled imperatively in a few lines. WinUI 3 has no equivalent built-in tree node model,
requiring a full custom FeatureTreeItem ViewModel with INotifyPropertyChanged, XAML value converters,
a RichTextBlock-based logger, and a NavigationService to replicate what was previously trivial.

Additionally, this project served as a hands-on migration from C# 7.3 to C# 14
adopting modern patterns including:

  • record types and init-only properties
  • Nullable reference types (string?, Button[]?)
  • Switch expressions (status switch { ... })
  • Target-typed new() and collection expressions
  • is not null pattern matching
  • Top-level using directives and file-scoped namespaces

For anyone coming from the WinForms version: the concepts are the same,
the implementation is almost entirely new.

Technical notes

β€’ Fully rebuilt UI: WinUI 3 (Windows App SDK 1.8)
β€’ Migrated from .NET Framework 4.8 (WinForms) to .NET 10 (Preview)
β€’ Mica backdrop, page-cached navigation, MVVM TreeView, plugin manager
β€’ Portable: No installer needed, just unzip and run

Included in the package:
β€’ Winslop.exe (main app)
β€’ Compiled XAML pages (*.xbf)
β€’ Plugins folder (optional)
β€’ .NET 10 runtime (self-contained, no install required)
β€’ Only English language resources
β€’ No MSIX/Store assets

Requirements:
β€’ Windows 10/11 (1809 or newer)
β€’ Windows App SDK Runtime (may need to be installed once)
β€’ No .NET installation needed
β€’ Windows App SDK DLLs (UI framework) needed

Release package:
Winslop-26.03.120.zip
The classic WinForms version is available as a legacy asset Winslop-26.3.31-legacy.zip for download.
The program folder now also includes Winslop.Legacy.exe if you still want to enjoy the classic version