I've spent some time today learning how to use the Entity Framework. Yesterday I skimmed over some of the content in the original Entity Framework section of the MSDN Library to get a bit of a background information.
But today's work has been focused on the 4.1 updated as that is what I will be using. I've been through the content in the Entity Framework 4.1 section . Sometime in the last couple of years I ended up referring to the MSDN Library documentation more, I had found it to have improved greatly compared to when I had first starting to use it. I cannot recall when they changed the layout and organisation, but I think it's made it a lot more useful.
So far I've been through these sections:
I've also covered most of the sub sections in these areas as well. The only two parts I have not looked at in these areas are the Azure and ASP.NET MVC pages. I have and don't want to setup a Azure account at the moment (though it could be an interesting thing to try someday) and I don't currently plan to use ASP.NET for this work so I will hold off on going through that testing.
All of the source I created can be found in my project on BitBucket named TestBed. I will use this for creating various testing projects so I can record the code. Here's the location https://bitbucket.org/kihonkai/testbed .
I tried both the WinForms and WPF binding examples to see what the differences were. It's interesting to see that the WinForms example requires an extra class to be define over the WPF example, a small hint that the developers are focusing on the use of WPF rather than WinForms. But then the WPF example ignores the hiding of the extra ID columns and the fact that its missing a data navigation toolbar like the WinForms system has. I've noticed this before, the WPF can do some interesting things but is still a new technology. Therefore the designer support and controls available etc are still a bit lacking compared to the WinForms alternatives.
Though I do still intend to use a WPF application as it will make working with the newer framework coding easier than having to add extra custom parts to make it work with the older WinForms system. Over time the WPF will surely improve and become as easy to use as WinForms.
I've still got a few topics left to review in the Entity Framework 4.1 documentation, once I've been through that I'm going to get started on the InfoLog application.