WPF Inspector

New Post: Not detecting Visual Studio 2010?

rloveless — Tue, 30 Apr 2013 14:43:22 GMT

I had this same problem. I was running Visual studio as administrator. If you run VS as administrator then you also have to run WPF inspector as Administrator for the detection to work.

Hope this helped.

New Post: Request a Feature

bsundsbo — Fri, 19 Apr 2013 09:34:39 GMT

Search visual tree for controls
Pin properties at the top for I am currently inspecting, and clear, as erikvullings suggests
Save screenshot! Allow the people who are writing documentation to use WPF Inspector to find the right control, and save a screenshot of the control only. Would make saving symbols much easier (same size, background, no noise)

New Post: Can't run this application in Windows XP，.net 4.0

GarfieldJiang — Sun, 31 Mar 2013 11:16:03 GMT

no idea.

New Post: Can't run this application in Windows XP，.net 4.0

meodudang — Fri, 29 Mar 2013 04:39:35 GMT

GarfieldJiang wrote:

I installed WPF inspector after installed .net framework 4.0 which worked well.But I received an error which said "Unable to find a version of the run this application".Some one can tell me why? Appreciate for any replay.

Same problem, any idea?

Created Issue: 64 bit Compatibility [1130]

vonbalaji — Fri, 22 Feb 2013 11:00:20 GMT

When I run the WPF inspector, it's not listing the application running in 64bit mode?

Are there any settings for attaching the applications under 64 bit ?

Thanks

Reviewed: WPF Inspector 0.9.9 (Jan 05, 2013)

glowysourworm — Sun, 06 Jan 2013 00:38:33 GMT

Rated 5 Stars (out of 5) - Dude.. You rule 20 different kinds of awesome. Nice work! Definitely a tool much needed in the WPF world

New Post: Export Property Grid

oszymczak — Fri, 19 Oct 2012 10:09:59 GMT

I was wondering if a export button could be added for the purpose of exporting the details of the property grid to csv or excel. What I'm trying to do is compare 2 elements.

Thanks

Created Issue: Feature: Support for NotifyPropertyChanged [1067]

mbendtsen — Tue, 02 Oct 2012 18:00:45 GMT

Could be nice to have a feature where you would be able to see a log of INotifyPropertyChanged.PropertyChanged and INotifyCollectionChanged.CollectionChanged events raised by the DataContext.
You should be able to see which property what was changed and which Action in the CollectionChanged event was performed (Add, Remove, Reset, Move).

Source code checked in, #19717

Project Collection Service Accounts — Mon, 01 Oct 2012 21:47:55 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #19716

Project Collection Service Accounts — Mon, 01 Oct 2012 21:46:19 GMT

Checked in by server upgrade

Reviewed: WPF Inspector 0.9.9 (sep 30, 2012)

SuperJMN — Sun, 30 Sep 2012 16:17:19 GMT

Rated 5 Stars (out of 5) - Gonna love this. Amazed from second one. And I came from Snoop WPF tool!!

Reviewed: WPF Inspector 0.9.9 (九月 25, 2012)

hillin — Wed, 26 Sep 2012 03:18:12 GMT

Rated 5 Stars (out of 5) - it's amazing. thanks dude

Created Issue: Elements tree display glitch [1054]

AccessD — Fri, 14 Sep 2012 05:49:06 GMT

When I'm selecting some element by Ctrl+LeftMouseButton element is focused in elements tree. Elements tree is expanded and scrolled to make selected element visible. But it is scrolled only vertically and if nesting is high, we can see just a blank view, because selected element is far to the right. I think elements tree content should be scrolled maximum to the right each time.

Created Issue: Slight incompatibility with .Net 4.5 [1037]

hamish — Mon, 20 Aug 2012 12:03:57 GMT

I realise nobody every claimed this would work with 4.5, but it doesn't seem to be very far off and I'm going to miss this tool until it's updated.

After I select any UI element either in the tree or using Ctrl+click, I get at least 400 Resource not found warnings in my application. These take a long time to run through, so it makes using the tool very slow.

Reviewed: WPF Inspector 0.9.7 (Aug 20, 2012)

ybonda — Mon, 20 Aug 2012 10:41:36 GMT

Rated 5 Stars (out of 5) - Very useful tool! I use it when developing WPF applications. Visit www.CodeArsenal.net for more info about WPF.

Reviewed: WPF Inspector 0.9.7 (Aug 20, 2012)

ybonda — Mon, 20 Aug 2012 10:41:10 GMT

Rated 5 Stars (out of 5) - Very useful tool! I use it when developing WPF applications. Visit www.CodeArsenal.net for more.

Reviewed: WPF Inspector 0.9.7 (Aug 20, 2012)

ybonda — Mon, 20 Aug 2012 10:40:36 GMT

Rated 5 Stars (out of 5) - Very useful tool! I use it when developing WPF applications. Visit CodeArsenal.net for more.

New Post: Trigger is too complex to expect. Problem

sashakirichek — Fri, 22 Jun 2012 09:31:58 GMT

I don't know what happens) Inspector just stop working when i point to some elements in my app.

Can i just turn of this option, or see error on tub of trigger expection to use other functions of the inspector?

It would be a nice feature.

Thnx for great program!

New Post: Not detecting Visual Studio 2010?

Gary2930 — Wed, 16 May 2012 10:31:57 GMT

I understood Visual Studio 2010 is a WPF application so why does WPF Inspector not detect it?

Is there a workaround?

Created Issue: Make readonly labeles copyable [925]

abatishchev — Thu, 26 Apr 2012 12:41:56 GMT

Readonly values on such tabs as Properties or DataContext can't be copied: text can't be selected, context menu contains no active items.
Please change that.