I can’t call this book Programming Windows because there’s already a famous and well-regarded series of books by Charles Petzold called Programming Windows. The other major question is what this should be called. So the first question is, should this be two books? Or one long book? I’m not sure yet. Plus, this is just the text: there are many screenshots and photos to add, so the book will be longer when those are added. NET era”) will be about the same length, but I guess I could be off, maybe even by as much as 100 pages. My guess, and it’s only a guess, is that the second half of the book (“the. So far, I’ve converted the first half of the series, the “pre-.NET era” part of the series, into 55 Markdown chapters that occupy 226 pages in PDF format. But there will be far more words, I bet, and far fewer screenshots. It’s not clear to me how many pages or words Programming Windows will be when the conversion to book is complete. But the question is, how big? For example, the Windows 11 Field Guide, which is unfinished, is currently well over 100,000 words long and is almost 700 pages in PDF form, largely because it’s chock full of screenshots. It’s also going to take some time, which raises some questions about how I’ll publish it.Īs a work, Programming Windows is big, like really big. I’ve been working to adapt the Programming Windows series, which is really a tech-centric history of Windows, into a book.

Programming windows 10 via uwp pdf