Windows SDK Team Releases First Part of the "Vista Developer Story"
Looking to learn about developing applications for Windows Vista? My team has posted the first part of the "Windows Vista Developer Story" to the MSDN Windows Vista Developer Center. This first set of content, "Top Ten Development Opportunities in Windows Vista", is just the first of thirteen different sets of content that we are planning on delivering biweekly in downloadable Help file (.chm) form. Among the future topics to be covered are:
- Commuication and Windows Commmunication Foundation
- Mobility, Tablet and other devices
- Presentation with Aero and Windows Presentation Foundation
- Secure Applications
- Install, Update and Shell
- Interoperability and Migration
- and many more
The next topic, Search and Organize, will be posted next week. Please let us know what you think of the content.
Comments
- Anonymous
January 16, 2006
Any chance of straight browsable html?
As a general rule I'm unlikely to download anything that's just "content", even if I'm moderately interested in the content. The same goes for stuff that's inexplicably available only in .doc format. If I'm really interested in the content I might download these things, muttering and complaining the whole time...
It's not like it's hard to export from ANY content-creation tool to HTML these days.
Don't get me started on how the C# language specification is no longer part of the local help in VS2005 (which I discovered when I was on the train with no internet connection, grr), and the online version is a DOC file that's still only a draft, and how it doesn't in fact cover the entire language but only the new features in 2.0, and how it isn't in fact correct because it doesn't incorporate the Nullable DCR...
Every time I need to switch contexts (web browser to word, web browser to whatever the heck you use to browse a CHM, VS internal help to web browser) is a minor pain, and if you add up enough minor pains you get to a major pain and people just won't read your content. It's the exact same thing as the overly-large-SDK-iso-only-download issue that I ranted about before, but in a different context ;)
Stuart.