Snoop's own version table stops at 6.0 while the releases are at 6.1.1
Snoop - The WPF Spy Utility
At a glance
- What is it?
- The WPF spy utility documents its history better than its current state: single-file applications are a 3.0.0 highlight and a present-day restriction, the fallback table has no row for either 6.1 release, the two build badges watch different branches, and the settings format that cascades over directory trees is never given a filename.
- Who is it for?
- Snoop is a working tool with an uneven page. The pieces a day to day user needs are all there, a global hotkey, two tracking modes with distinct modifier combinations, a way to hide properties nobody should edit, and settings that follow a directory tree so a team can share one setup.
- Can I use it commercially?
- Yes. MS-PL is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 84 days ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- snoopwpf/snoopwpf2,549 ★ · +11
| Repository | 2026-10-01 | 2026-11-15 |
|---|---|---|
| snoopwpf/snoopwpf | 2.5k | 2.5k |
11 Stars in the last 45 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The default branch is develop and one of the two build badges tracks master
Snoop's recorded default branch is develop, and the two badges at the top of the page disagree about which branch they watch. One points at the AppVeyor build for `branch/master`, the other at the AppVeyor build for `branch/develop`. So the page advertises a CI result for a branch that is not the default one, and the two badges cannot both be describing the same commit.
The build story is just as plural. The repository root holds `build.cmd`, `build.ps1`, `build.sh`, a `.build/` directory and a `.nuke/` directory, plus three files named `Directory.build.props`, `Directory.build.targets` and `Directory.packages.props`. What the page tells you to do is none of that. It says to open `Snoop.sln` with Visual Studio and build it, and lists the requirements as Visual Studio 2022 or later with C++ payloads for x86 and x64 and optionally ARM and ARM64, a `.vsconfig` file you can import so the installer pulls in every required component, and .NET SDK 10.0.100 or later.
Single-file applications were a 3.0.0 highlight and are now the stated restriction
Read the changelog forwards and one headline capability reverses. The 3.0.0 notes list support for .NET Core across 3.0, 3.1 and 5.0, explicitly including self-contained and single file applications, alongside a rewritten injector and the removal of any need to install a Microsoft Visual C++ Redistributable. That same version carries a known issue: trying to snoop a trimmed single file application might not work, because trimming may have removed things Snoop relies on.
The current Supported .NET versions section then states a flat restriction, that self-contained single file applications are not supported since there is no reliable way to get a handle to the .NET runtime. So a feature listed as a highlight in 3.0.0 is now an exclusion, and the stated reason has moved from trimming removing types to the runtime being unreachable at all. The rest of the .NET line stays open ended: .NET >= 6 is supported, tested with 6, 7, 8, 9 and 10, and the page notes that future versions might just work.
The compatibility table stops at 6.0 and covers neither current release
The section headed Why can't I snoop my application? answers with a table of minimum versions and four rows: Snoop 3.0 against .NET Framework 4.0 and .NET 3.0, Snoop 4.0 against 4.5.1 and 3.0, Snoop 5.0 against 4.5.2 and 3.1, and Snoop 6.0 against 4.6.2 and 6.0. The answer it gives is that you can snoop your application, you just need an earlier version of Snoop.
But the release list has moved past that table. The most recent releases are v6.0.0 from 2025-05-24, v6.1.0 from 2026-04-26 and v6.1.1 from 2026-05-24, and neither 6.1 release has a row. Nothing on the page links the older Snoop builds it is telling you to fall back to, so the fallback is a version number with no path attached. The table also encodes the policy the changelog states in prose: 6.0.0 dropped every .NET Framework version prior to 4.6.2, along with .NET 3.1 and .NET 5.
Changelog links mix tagged and untagged release names
Seven version sections link to their release pages, and they are written two different ways. The 3.0.0, 4.0.0, 5.0.0 and 6.0.0 headings point at addresses shaped like `../../releases/tag/v6.0.0`, with a `v` prefix. The 2.9.0, 2.10.0 and 2.11.0 headings drop the prefix and point at `../../releases/tag/2.11.0` instead. The three older entries also read differently in every other respect. Each states its release date in prose rather than in a list, 2.9.0 on July 27th 2018 and 2.10.0 on September 19th 2018, and 2.11.0 carries no date at all.
Those addresses are relative and begin with `../../`, two levels above the directory the README sits in, so they resolve only in a page view that rewrites repository relative links. The Download section by contrast uses absolute addresses for all three sources. The newest dated sentence anywhere on the page is from 2018, while the release list runs to 2026, so the prose history and the artifact history have drifted apart at exactly the point where the version numbers start to matter.
A tool for .NET 6 and later still asks for .NET Framework 4.6.2
The download section lists three sources with different promises. Chocolatey carries stable and some preview versions, GitHub releases carry stable versions, and AppVeyor carries the latest preview versions, built on every code change. Below that list sits one line with no version negotiation in it at all: you need at least .NET Framework 4.6.2 to run Snoop. That floor is stated even though the supported list directly above puts .NET Framework >= 4.6.2 and .NET >= 6 side by side, so the tool for the modern .NET line still names a .NET Framework requirement for the machine it runs on.
Signing is handled separately. The 4.0.0 notes record that artifacts are digitally signed thanks to SignPath.io, and name the artifacts as MSI, Chocolatey NUPKG and zip. The Code Signing section at the foot of the page credits SignPath.io for the signing service and the SignPath Foundation for a free code signing certificate, and its second link stops partway through the address. The page does not say which artifacts that signing covers, so a preview pulled from a per-commit build is on different footing from a signed MSI.
Settings cascade over directory trees and the file that holds them is never named
The 5.0.0 notes replaced the settings system with one that does not rely on `System.Configuration`. Two properties of the replacement are stated plainly: settings can be shared between different snooped applications, and settings can be defined for whole directory trees. Both matter for anyone automating this, and neither is followed by a filename, a format, or a statement of which value wins when the same setting appears at several levels of that tree.
The same version added the ability to hide properties from the default view, and gives the whole mechanism as one line: annotate the property with `[System.ComponentModel.BrowsableAttribute(false)]`, written out in full with the namespace spelled out rather than shortened. Nothing on the page says how Snoop decides which directory tree to read, or what it does when the nearest directory holds nothing. The result is a feature whose behaviour you can only partly predict from the description, and a directory-level convention that has to be recovered from the source.
Three videos stand in for the documentation the page says it does not have
There is a section on documentation, and it opens by conceding the point: there is not any exhaustive documentation on how to use Snoop, and there are plenty of hidden features. It asks for volunteers, then argues the other side, that it is a pretty easy utility to use and learn, and offers three YouTube videos as the substitute.
The section headings around it are not in the shape the rest of the page uses. One reads `## Where can i download Snoop?/How can i install Snoop?`, a lowercase i and two questions welded together with `?/` rather than split into two headings. Another reads `## How do i build Snoop?`. So the two sections a newcomer most often needs are also the two whose headings are malformed, and a reader scanning for downloads or build instructions is the reader most likely to skim past them. The easy to learn claim has exactly one concrete anchor on the page: start Snoop, focus a WPF application, and press `CTRL + WIN + ALT + F12` for the global hotkey.
The triggers tab is a port, and contact still points at Gitter and Twitter
The 2.9.0 entry explains where a feature came from. The triggers tab was included because it was a useful feature of another WPF spying utility called WPF Inspector, and it was ported to Snoop by the current maintainer. That is the only other product the page names, and it appears as a source of code rather than as an alternative on a menu.
Two smaller points round out the page's own description of itself. Contact is two links, a Gitter lobby room and a Twitter account. And the licence is the Microsoft Public License, with two copies of it at the repository root, License.rtf and License.txt, which is worth knowing if you go looking for the terms in a format you expected. The contributor list credits the original creator, the current maintainer and five further people. The repository itself is not archived, shows 2538 stars, 402 forks and 17 open issues, and the last push to the develop branch is dated 2026-08-23.
Editorial conclusion
Snoop is a working tool with an uneven page. The pieces a day to day user needs are all there, a global hotkey, two tracking modes with distinct modifier combinations, a way to hide properties nobody should edit, and settings that follow a directory tree so a team can share one setup. What the page does not give you is a version story you can act on. The fallback table stops at Snoop 6.0 and names neither of the two releases you would actually install today, the support for single file applications listed as a 3.0.0 highlight is now the stated restriction, and the build badges watch two different branches. Before making it part of a workflow, match your Snoop version to your target's .NET version using the changelog rather than the table, and read the source for the settings format, since no filename is given for it anywhere.
Frequently asked questions
What is Snoop?
It is an open source WPF spying utility, originally created by Pete Blois and currently maintained by Bastian Schmidt. It attaches to a running WPF application without a debugger so you can browse the visual, logical and automation trees, change property values, view triggers and set breakpoints on property changes.
how to install snoop wpf
Three sources are listed: Chocolatey for stable and some preview versions, GitHub releases for stable versions, and AppVeyor for the latest previews, which are built on every code change. You need at least .NET Framework 4.6.2 to run Snoop, and the supported list is .NET Framework 4.6.2 or later alongside .NET 6 or later.
how to use snoop wpf
Start Snoop, focus a WPF application and press CTRL + WIN + ALT + F12 for the global hotkey. Holding CTRL + SHIFT snoops controls that are otherwise disabled, while CTRL + ALT skips template parts and CTRL + SHIFT does not. The page admits there is no exhaustive documentation and points to three videos instead.
snoop wpf alternative
The only other product the page names is WPF Inspector, another WPF spying utility, and it appears in the 2.9.0 notes because its triggers tab was ported into Snoop. For an application your .NET version cannot reach, the page's own answer is to fall back to an earlier version of Snoop.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/snoopwpf-snoopwpf)Star history chart for your README
[](https://hysenlabs.com/projects/snoopwpf-snoopwpf)Was this useful?