|Although I started with Cold Fusion for application development, I did plenty brochureware sites with HTML. I believe the version was HTML 2.0 for IE 2.0. I lived in the browser world for years doing Cold Fusion, ASP, and HTML sites. When winforms and Smart Client with web services emerged I changed my religion. Since then I have been avoiding the browser whenever possible since.|
Microsoft has recreated the same type of migration path as they did for the VB6 developers to move to VB.NET. The problem with that migration was tons of really bad VB.NET being written. After running into a lot of VB.NET projects that performed very badly and were very buggy I refused to allow VB.NET on my projects whenever I could.
The problem was VB6 programmers would not learn OOP and continued to code like they were still in the VB6 world. When I made them switch to C# that seemed to force them to learn more about .NET and that really helped improve their OOP skills. I never had anything against VB.NET coded correctly, the problem was most people didn’t code it correctly.
1. Hello, Windows 8!
2. Binding and Controls
6. Drawing and Animation
7. App State
9. Shell Contracts
10. Shell Integration
11. Device Interaction
12. Native Extensibility
13. Making Money
B. Presentation and Style at a Glance
The application state coverage is an important topic to understand and a must read chapter for new Windows 8 App developers.
I thought they did a really good job of covering Shell Contracts and Shell Integration. They are one of my favorite features in Windows 8.
The last chapter of the book does an awesome job of showing us how to go through a submission to the Microsoft Windows Store.
I did find a couple of things missing that I would have like to see covered. One was the Windows.UI.Input.Inking APIs. The was no coverage at all. This is one of the main features I am using in the XAML project I am building. Another topic I would have liked to have seen more on in is using SQLite. So far all the books that I have read on Windows 8 Apps tell you that it's available, but they don't explain how to use it. The apps I am working on are going to need a robust local data cache, and App Data and User Data are not going to be able to handle it. Security was also only lightly touched on. There could have more on security.
The code samples are very well organized and usable. The best part about them is they all work. That is not always the case anymore. I recently purchased a book I had been really looking forward to getting my hands on. It had 11 projects included as samples and none of them worked. After going back and forth with the author I threw the book on a shelf and decided to not even bother with it. He fixed three of them by the third round of updates. That gave me very little confidence in the advice he would offer in a book.
For more book recommendations check out my .NET, iOS, and Java Architecture and Development Book Recommendations for 2013