I just thought I would point you to a cool feature in Snoop in regards to binding errors. There is an editable combo box above the visual tree that allows you to filter the visual tree. But, if you pull down the combo box, you can select an item in the combo box that states ‘Show only visuals with binding errors’. This item will filter the tree to only the items that have data binding issues. (To clear the filter, select the editable text in the combo box and just hit the delete key.)

Just a tip for being so kind!

You are my best friend now. Careful, some people might not be happy if I told them that!

But anyway, Snoop helped me find a binding error that has been messing with me for about 3 days. Driving me nuts! I haven’t found WPF to be too helpful at pointing out binding problems. It just quietly doesn’t work. No exception, no complaining, it just doesn’t work!

This problem is why I was looking for a tool like Snoop last night. When I found Snoop, it looked like it might help me solve my problem. This morning, once I figured out what it could do and how to work it (still feebly I must admit), I quickly found the problem.

I hope that you are having a great day … I am now.

Les

I hope to actually record some quick 5 minute screen casts, posting them to my blog and to the http://snoopwpf.codeplex.com site.

I also plan on building out the documentation section of the CodePlex site.

However, for now, the best source of info on how to use it, would be at Pete Blois’ site. Just scroll down a little.

Glad to hear that you’re loving Snoop. It is an extremely useful little utility for WPF (for learning, diagnosing, and more).

That is, if you want to Snoop a 32-bit application that has been built with WPF 3.5, you need that version. If you want to Snoop a 32-bit application that has been built with WPF 4.0, you need that version … and so on.

I hope to fix this in the near future … as a fellow has already sent me changes to Snoop such that there is only one version and it figures out for itself how to handle the different situations. But as it stands, right now, you have to do that yourself.

I bring this up … because you mentioned only seeing Visual Studio (with your application that you want to Snoop) in the application chooser’s combo box. This is because Visual Studio runs as a 32-bit application. I would speculate at this point, that the application you want to Snoop is a 64-bit application. Thus, if it is a WPF 4.0 application, you would need the WPF 4.0, 64-bit version of Snoop to do so.

Again, I hope to fix this soon.

Wow! Been messing around with it. This is looking good now. I held down Ctrl-Shft, moused around the app and things became alive. I can find things that my mama didn’t know about or where they are.

Hey thanks Cory, it is late now but I can’t wait until tomorrow morning to get started at some depth. Please think about a quick start tutorial for dummies or something. Maybe with levels like 101, 201, 301, 401, graduate and post grad. This is really telling me a lot about WPF!

I just downloaded it. I have a WPF 4.0 app running and would like to “Snoop” it. I click “Refresh” and expect that all the WPF applications would show up in the combo box but still nothing.

How can I figure out how to get started with this cool tool? It sounds very useful and simple to use, but I am having no luck.

Please help get me off the ground.

Thanks,
Les

It was quite an interesting problem!

I was just wondering if there is any licensed version of Snoop to buy. If yes, kindly provide me the details ASAP.