Just installed VS 2008 beta and had a first look at what WPF and the new VS
offer.
A couple of quick notes.
Using WPF is more like using Visual Web Developer since there is a split in
the UI between the visual and the XAML.
The IDE does not seem much changed but there are intellisence "improvemen ts"
which I am not sure I like.
The worst part of what I see is the lack of migration path from Windows
Forms to WPF. While WPF offers much more visual control over the controls
and how they behave to the user it seems that alot of things you have
learned using Windows Forms are no longer valid.
To illustrate lets look at the code for one of the commonly asked questions
in this forum. "How do I click a button from my code". Now in Windows
Forms this is simple but the code for WPF is as follows:
dim bap as ButtonAutomatio nPeer = new ButtonAutomatio nPeer(myButton)
dim iip as IInvokeProvider = bap.GetPattern( PatternInterfac e.Invoke)
iip.Invoke() ' This clicks the Button
I think all the people who endured the move from VB Classic to VB.NET will
freak out seeing that much of their current knowledge about the UI goes out
the door. At least the major data classes and OS hooks are the same.
Just my first two cents about the new tech.
Lloyd Sheen
offer.
A couple of quick notes.
Using WPF is more like using Visual Web Developer since there is a split in
the UI between the visual and the XAML.
The IDE does not seem much changed but there are intellisence "improvemen ts"
which I am not sure I like.
The worst part of what I see is the lack of migration path from Windows
Forms to WPF. While WPF offers much more visual control over the controls
and how they behave to the user it seems that alot of things you have
learned using Windows Forms are no longer valid.
To illustrate lets look at the code for one of the commonly asked questions
in this forum. "How do I click a button from my code". Now in Windows
Forms this is simple but the code for WPF is as follows:
dim bap as ButtonAutomatio nPeer = new ButtonAutomatio nPeer(myButton)
dim iip as IInvokeProvider = bap.GetPattern( PatternInterfac e.Invoke)
iip.Invoke() ' This clicks the Button
I think all the people who endured the move from VB Classic to VB.NET will
freak out seeing that much of their current knowledge about the UI goes out
the door. At least the major data classes and OS hooks are the same.
Just my first two cents about the new tech.
Lloyd Sheen