|
I wouldn't go back to MFC or Winforms after WPF. There is certainly a learning cliff and no book is going to take that away. Its just a whole different way of thinking. Winforms is pretty much just a managed version of MFC, so there isn't a curve at all once you know C#. WPF introduces a ton of new concepts and when you do WPF "the right way" and throw MVVM into the mix, its more an abyss then a cliff.
|
|
|
|
|
SledgeHammer01 wrote: more an abyss then a cliff
Hah, very encouraging. 
It’s not because things are difficult that we do not dare, it’s because we do not dare that things are difficult. ~Seneca
|
|
|
|
|
Well, I learned WPF the non-MVVM way and then learned MVVM later on. Now that I know both, I'd recommend learning both at the same time because non-MVVM WPF can be quite the mess.
|
|
|
|
|
Thanks. 
It’s not because things are difficult that we do not dare, it’s because we do not dare that things are difficult. ~Seneca
|
|
|
|
|
That's a fair point and something that is absolutely not covered by WPF Unleashed.
If you find a similarly well-written book about MVVM, I'd be interested.
|
|
|
|
|
I learnt WPF from that book. It's a very good starting point and I often find myself going back to it when I need a reminder.
Not too dry and lots of examples and pictures which are a must when you are trying to explain the visual aspects of WPF.
|
|
|
|
|
Thanks. Yes, I'm already getting into it. One of the things I really like - in addition to what you mentioned - is that he gives the equivalent code in C# to the XAML. That really helps me learn and 'see' what's happening. I know it's a huge subject and I'm now just going to jump straight in.
It’s not because things are difficult that we do not dare, it’s because we do not dare that things are difficult. ~Seneca
|
|
|
|
|
Honestly, and this is kind of my opinion about most programming books... they are usually structured in the same way:
Chapter 1: Feature X
Short Summary of Feature X
A few small examples that cover 13% of Feature X
Chapter 2: Feature Y
Short Summary of Feature Y
A few small examples that cover 9% of Feature Y
etc.
They never really show how features X & Y are inter-related or how they are important in the big picture.
I've never written a book myself, but I think if I were to write a WPF MVVM book, it would be something like "In this book we are going to write Application.exe from start to finish... we will cover all the design and architecture issues and show you how all the pieces come together with detailed explanations. In the end, you'll end up with a light weight MVVM framework that you can use on other applications".
That seems common sense to me... rather then giving you a bunch of random snippets about random features.
|
|
|
|
|
Annie - do you have a background in ASP.NET? If you do, try to think in terms of how that works, rather than the way WinForms works. It really helps you to understand XAML if you approach it from the markup side.
|
|
|
|
|
No. I've never done any ASP.NET. But, thanks for the advice about learning the markup. I was getting a bit confused as Nathan provides a lot of the C# code and wasn't sure which way to go.
I'm just going to dive in as I have a small project I need to start today which will involve quite a lot of data binding. I'll come here if I need help! Thanks for the support.
It’s not because things are difficult that we do not dare, it’s because we do not dare that things are difficult. ~Seneca
|
|
|
|
|
That's kewl  . Buy the book Wednesday, start the project Friday. I definitely like your style
When I was a coder, we worked on algorithms. Today, we memorize APIs for countless libraries — those libraries have the algorithms - Eric Allman
|
|
|
|
|
Read my tag-line
It’s not because things are difficult that we do not dare, it’s because we do not dare that things are difficult. ~Seneca
|
|
|
|
|
He who dares, wins! You sound like a winner. Go for it, I say. Oh, and good luck with the project.
When I was a coder, we worked on algorithms. Today, we memorize APIs for countless libraries — those libraries have the algorithms - Eric Allman
|
|
|
|
|
Her tag should actually read "she who dares bakes"
|
|
|
|
|
Do you want the recipe for my World Famous Shortbread?
It’s not because things are difficult that we do not dare, it’s because we do not dare that things are difficult. ~Seneca
|
|
|
|
|
|
How? You have no email link. Please advise!
It’s not because things are difficult that we do not dare, it’s because we do not dare that things are difficult. ~Seneca
|
|
|
|
|
display image in grid in silverlight
|
|
|
|
|
By using an Image control.
|
|
|
|
|
I'm working on a WPF application.
I'm getting the complile time error
The type reference cannot find a public type named 'OperatorModel'. Line 14 Position 51.
Here's the XAML:
<Window x:Class="Services.Late2Lien.UI.Views.MainWindow"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation"
xmlns:local="Services.Late2Lien.UI"
xmlns:models="Services.Late2Lien.Models;assembly=Services.Late2Lien.Models"
Title="Walz Late2Lien"
Height="596"
Width="786">
<Window.Resources>
<HierarchicalDataTemplate DataType="{x:Type models:OperatorModel}"
ItemsSource="{Binding Path=Facilities}">
</HierarchicalDataTemplate>
It's failing on the HierarchicalDataTemplate line.
The Models are in a seperate project in the solution called Services.Late2Lien.Models and the project is referenced in this project.
When creating the xmlns:models tag, intellisense does NOT show the Services.Late2Lien.Models namespace.
I've seen this problem before, and there's alot of Google hits about it, but I can't seem to resolve it. Anyone see what's wrong here?
Thanks
Everything makes sense in someone's mind
|
|
|
|
|
Trying doing a clean and build.
Too much of heaven can bring you underground
Heaven can always turn around
Too much of heaven, our life is all hell bound
Heaven, the kill that makes no sound
|
|
|
|
|
Did that already
[UPDATE]
I removed the reference to the Models project an created a reference to the Models.dll and now it works.
Everything makes sense in someone's mind
modified 27-Sep-11 13:42pm.
|
|
|
|
|
Hello Everyone,
An Image which is below the listview. Listview contains some small images and their names.
I want to change the below image on mouseover of listview Item.
Thanks in Advance
Ashish Parmar
|
|
|
|
|
Just thinking aloud
Use the mouseover event to select the item in the listview and bind the image to the uri of the selected item.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
That's perfectly Fine...
But I want to know about the code in XAML..
how can i define code in XAML to have this functionallity..
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
