I tried to use WPF for the first time today and noticed that it is very buggy. I get random errors, windows don't work the way they should, the designer keeps going black and is out of date. Ranaming a window in solution explorer fails to update the window name in code and in namespaces so I have to edit every line manually.
I was trying to create a simple MDI application which it appears is no longer supported. I've tried to test if a window was disposed using the .IsDisposed property which is missing now as well. I can't figure out how to test for a window that is disposed or waiting to be disposed.
I guess for now I am going to stick with Windows Forms because it seems like WPF has a long way to go yet...
Use Expressions Design for your WPF needs. v3 is coming out soon
I'm don't know what you mean by expressions design. I was just playing with WPF because I heard that it was going to replace windows forms. I don't know if that is true or not. For now I can continue to use windows forms and get a faster result. If there is a new version of WPF coming out soon I will wait to try that version.
WPF was released well over a year ago [2/19/2008] and is extremely reliable with plenty of large scale busiless applications implemented using this technology.
Because of fundamental philosophical differences between this technology and other UI technologies, new users often mis-interpret thier own errors as a problem with WPF.
As previously mentioned, much of the work can (and usually should) be done with one of the design tools in the Expression suite of products. There is lots of good information at: http://blogs.msdn.com/expression/default.aspx and I recomend all people looking at WPF to spend at least a few days going through the material on this site.
TheCPUWizard is a registered trademark, all rights reserved. (If this post was helpful, please RATE it!)
2008, 2009 In theory, there is no difference between theory and paractice; in practice there is.
* Join the fight, refuse to respond to posts that contain code outside of [code] ... [/code] tags. See here for instructions
* How NOT to post a question here
* Of course you read this carefully before you posted
* Need homework help? Read this first
I was about to reply something exactly along the lines of what TheCPUWizard said... I fully agree. By now, WPF is long being productively used used in more and more large-scale projects.
However, I agree that the integrated XAML designer in VS 2008 still has a long way to come - it's still work in progress, and, for many scenarios, close to unusable. Therefore, in real-world projects, as a developer, you'll find yourself hand-coding XAML most of the time.
Expression Blend does a pretty good task as a XAML editor, but it is originally not targeting developers, but professional designers, and more specifically, those who are familiar with Adobe's Flash tools.