>>I agree it would be better if the properties window picked up info from the code behind. I haven't looked properly at VS2010 yet but I don't recall seeing anything about changes in this respect.
>>
>>But, TBH, I can't say I've found this particularly important. This may be down to the fact that I now very rarely use the properties window (even to inspect values) but rely almost entirely on working directly with the XAML or code behind. The same is true of the design view - I have it open to check how things look but almost never use it to pull in items from the toolbox or to adjust the layout - again I do this pretty much exclusively in XAML. I'm much more likely to have the 'Document Outline' window open than the properties window. I would hazard a guess that you will tend to adapt the same methodology as using XAML becomes more natural.
>
>Well, I've just read that I shouldn't be thinking about events and eventhandling in the "WinForms" sense. ICommand and CommandBinding is the proper methodology for WPF, along with the MVVM design pattern, so I'm delving into that now. Hopefully I'll have one of those "ah-hah" moments soon.
>
>~~Bonnie

Hah! Just wait til you get to routed events... :o)