OK, I see what you're saying. You're doing layout with the designer and seeing the XAML is changing.
Yes, the XAML is the underlying representation of the layout. i think most people are thinking about the code that gets generated and called via "InitializeComponent". What gets generated after the XAML compiler parses the XAML.
You should view the designer as simply a convenient way to edit XAML. Like using a designer to edit HTML.
MVVM is sort of like MVC, although really closer to MVP. Think of MVVM as MVP that where databinding coupled with the View Model is the Presenter.
Comments
OK, I see what you're saying. You're doing layout with the designer and seeing the XAML is changing.
Yes, the XAML is the underlying representation of the layout. i think most people are thinking about the code that gets generated and called via "InitializeComponent". What gets generated after the XAML compiler parses the XAML.
You should view the designer as simply a convenient way to edit XAML. Like using a designer to edit HTML.
MVVM is sort of like MVC, although really closer to MVP. Think of MVVM as MVP that where databinding coupled with the View Model is the Presenter.
I'd say ui designer is convenient at the cost of potentially adding cruft, again not much different than using say dreamweaver.
I've been doing WPF for a the past year, and I've learned to just edit XAML manually while staring at the designer for instant feedback.