Backgrounder needed. Why WPF

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I have been through two books where they talk about the (almost)
parallel control set for WPF and VB. They go through the small
difference and talk about everything going on a form but what they don't
say is...

WHY WPF?

What did we get by having a (almost) parallel design palette. If the
features were so good, why not just fold them into the parallel controls
in VB?

This makes for another set of hundreds of things to remember and I can't
see the overriding benefit.

Possibly there is a White Paper on this somewhere or someone in the know
can say why. Wrox book talk about the what but not why this duality
came about.

Thanks for any help with this. I can't help but think that two
competing groups of designers got to load their almost identical but
incompatible stuff into the same IDE. Just seems odd to me. Anyone
else?

Mike

-----------------------------------------------------------

There are a variety of enhancements to the WPF Designer that are not
available in the Windows Forms Designer. These enhancements include:

Margin lines and stubs: Margin lines around each control indicate that a
margin has been set for that control. A margin stub indicates that no
margin has been set for that control edge.

Zoom control: The Zoom control appears in the upper-left corner of
Design view and allows the developer to zoom in or out on the design
surface to perform exact adjustments.

Snaplines: While snaplines appear in both the WPF Designer and the
Windows Forms Designer, in the WPF Designer they also display exact
values. In addition to displaying control alignment, snaplines also show
text alignment for text-based controls. For more information, see How
to: Align to Both Text Baselines and Margins.


.

Relevant Pages

  • Re: Backgrounder needed. Why WPF
    ... MS have clearly opted to invest into WPF, XAML, Silverlight, ... parallel control set for WPF and VB. ... There are a variety of enhancements to the WPF Designer that are not ... Margin lines and stubs: Margin lines around each control indicate that a ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Backgrounder needed. Why WPF
    ... WPF is redesigned while Windows Forms still builds on the good old concepts ... the template for a control you can customize its appearance much more easily ... There are a variety of enhancements to the WPF Designer that are not ... Margin lines and stubs: Margin lines around each control indicate that a ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Re: Backgrounder needed. Why WPF
    ... MS have clearly opted to invest into WPF, XAML, Silverlight, ... parallel control set for WPF and VB. ... There are a variety of enhancements to the WPF Designer that are not ... Margin lines and stubs: Margin lines around each control indicate that a ...
    (microsoft.public.dotnet.languages.vb)
  • Re: PDA application development
    ... Chris Tacke, Embedded MVP ... To get it to even work at all - not considering designer support ... write a COM interop wrapper around the control. ... "Michael Salamone" wrote: ...
    (microsoft.public.pocketpc.developer)
  • Re: Disappearing Controls when the designer loads a form.
    ... which were traced to an exception my user control threw while in the designer. ... private ArrayList readOnlyColumnsList; ... public string ReadOnlyColumns ...
    (microsoft.public.dotnet.framework.windowsforms.designtime)