How long to learn wpf

Just browse here in CP Posted Apr pm thatraja. I would strongly suggest that you get a good book first. Posted Apr am Nish Nishant. Posted Apr pm demouser You need not look any further than Code Project. It will be a learning curve but I strongly recommend focusing on doing it. I would also recommend you look into some of the frameworks as this will speed up development. It will also give you time as you will not have to write many of the functions and methods that help with MVVM and wpf application development.

Posted 7-May am db7uk. Start learning WPF from this video, its a full learning series. Posted 9-Mar pm Shivprasad koirala. You can try "Beginning WPF 4. This book is very helpful for the Beginner. The examples in this book will include every single line of code that is required to execute. No assumptions will be made. Posted 7-May am Blake. Add your solution here.

OK Paste as. Treat my content as plain text, not as HTML. Existing Members Sign in to your account. We hope that this tutorial will get you started properly on WPF. A basic knowledge of C is recommended when learning to use WPF.

If you don't already know some C , you may wish to get a better sense of by going through a C tutorial. We hope you like this tutorial and if you do, please help us by linking to it from your website and share it with your friends on social media like Facebook and Twitter.

Would you prefer to read this tutorial in another language? Once you get used to the model, though, going back to other APIs is painful. Not because they're suddenly hard, but because you know how easy things can be. As you might be able to infer from my question history, I definitely have found it to be a steep learning curve. You describe my experience almost exactly.

As a full-time student in math and physics, not software engineering who only does WPF programming for hobbyist applications, it's been rather frustrating. I've tried creating new applications in WPF, or porting some of my old applications over to WPF, and always get stuck on some small little thing that seems inordinately hard. One thing I haven't donebasically because of time concernsis sit down with e.

If you're a professional developer, that might be much more doable, and might make WPF much easier for you. The biggest thing that gives me trouble, I think, is getting my head around the Model-View-ViewModel paradigm see e. Whereas in WinForms I could just drag and drop some stuff onto a form, mess with its properties, and hook up some events in the codebehind, now I have to think about partitioning things into view, model, and viewmodel.

A lot of those codebehind events become validation rules or databinding stuff. It probably doesn't help that none of my applications are really "data manipulation" applications; that is, they don't manipulate a database of customer info or anything, where a lot of this would make sense. Instead it's more like "I want a textbox that the user enters a URI into, and I want the button that says 'Download' to only be enabled if that textbox contains a valid URI.

Another annoying issue is how many things are just plain missing from the framework. For example, sorting listviews. In the end, though, WPF has a lot of advantages. The layout framework seems a lot nicer than the primarily pixel-based WinForms model. It uses modern fonts like Segoe UI, heh :P. And its compositing features are pretty awesome too, e.

I have been playing with. NET for more than 4 years, mostly Windows Forms applications. Binding is not something unknown and I try to use good practice in all my C applications. You can do a lot more and achieve some cool designs with less effort but only once you know how it really works and it's hard because it's huge.

More, debugging is harder - that makes the learning more slow too. I like it but yes, the learning curve is not smooth.

I spent the better part of a month experimenting with WPF and writing a mock-up of our current product in it without developing an intuition for its databinding model or even figuring out how Microsoft means for it to be used. It took me much less time to grasp the basics of ASP. Perhaps another book would have been more appropriate. The biggest problem is working out if it is worth it at all and there is still a lot of applications that would be fine implemented as Windows Forms plus a bit of graphics.

I would also agree with the earlier comment about getting into XAML - it's just like a slightly more sophisticated HTML and the only real difficulty is finding out what does what. As for getting stuck later on in a project - don't you always get stuck later on in a project? Yes, it is not an easy walk - but be not afraid. The thing about WPF, it is beautifully engineered so you get a constant positive emotional feedback at least I did ; when learning it.

You like sitting playing with it and exclaim "WOW" every few minutes ;. It's going to be one of those 'it depends' answers but all it really depends on is if you're the kind of developer that tries to continually improve your skills.

If that's the case then it comes down to a couple of things ultimately. Buy WPF Unleashed others books are available but I whole-heatedly recommend this one , work through the examples and in about 2 months or so you'll wonder how you ever got things done without it.

It's not rocket science and there are no paradigm shifting concepts to deal with. In fact, if you are used to keeping a good separation between your logic and presentation it should fit right in. From the few people I worked with that had to learn it, they really recommend going through all the tutorials from Expression Blend. That gave them a good background on WPF and the better tool to use when working with it. If you have experience with HTML or XML or similarly based languages, it's not exceptionally difficult, especially if you have web design experience.

If you're coming strictly from a WinForms background, the learning curve is a bit steeper. I am currently learning WPF myself and since I come from an extensive web development background, I'm not finding the concepts all that difficult to master for most of them.

I've found the online tutorial videos at WindowsClient. How are we doing? Please help us improve Stack Overflow.