What's the WPF equivalent of WinForms components?
components, winforms, wpf
Solution
Just from my own observations, it seems like Microsoft is trying to move away from having components and similar things in the GUI. I think WPF tries to limit most of what's in the XAML to strictly GUI things. Data binding I guess would be the only exception. I know I try to keep most everything else in the code-behind or in separate classes or assemblies.
Probably not exactly the answer you wanted, but it's my $0.02.
Problem
Windows Forms allows you to develop Components, non-visual elements that can have a designer. Built-in components include the BackgroundWorker, Timer, and a lot of ADO .NET objects. It's a nice way to provide easy configuration of a complicated object, and it it enables designer-assisted data binding. I've been looking at WPF, and it doesn't seem like there's any concept of components. Am I right about this? Is there some method of creating components (or something like a component) that I've missed? I've accepted Bob's answer because after a lot of research I feel like fancy Adorners are probably the only way to do this.