Trivial may be those tasks that are really easy to do, from what I saw in your sample, the information can be classified as "trivial" nontheless I liked to see those screenshots, (the short cut parts are the best in the way you are showing them).

Zain,

I think your shortcut for Free your document windows is wrong! Same for Insert Document to the right of existing tabs

You have ALT+W, F(float) and ALT+W, T(dock)

It should be:

ALT, W, F (float) and ALT, W, T(dock)

There is a big distinction!

If nothing is bound to the shortcut key ALT+W then that will drop down the menu for Tools, but if you have something bound to ALT+W,T, then only

ALT,W,T will select the menu item

Hi Zain,

in my opinion you are using too much screenshots in your book. It is enough to write "Just go to Tools | Options | Environment | Documents and select the Insert Documents To The Right Of Existing Tabs option." A screenshot is not needed. Maybe 300 pages are enough, if you skip some screenshots.

Michael

I agree with the previous comments about too many screenshots. After reading the bit about inserting documents to the right of existing tabs instead of the left I thought, so what, what difference does it make? So it might be nice to explain the benefit of some of these options, where it makes sense.

How about a glossary with screenshots? Most readers, including me, do not know a Guide Diamond. Instead of showing a screenshot of the Guide Diamond in every tip, just show one screenshot in a glossary. Or start the book with an introduction where you explain the basics of the visual studio ide.

Michael

I like Michael's idea of a glossary, or intro section, that explains some product specific terms that could be used as a reference. I also agree with others on screenshots are nice, but some are self-eplanatory such as the inserting documents to right of tabs. I'd like to see less screenshots of the options dialog, only use screenshots if the option isn't obvious to find.

I also agree that eliminating the everyday, covered in 1000s of books already, tips; such as setting break points. Stick to tips that we may not be aware of; leave the beginner tutorial tips to the beginner books that are a dime a dozen. Tips like how to change the tab to align to right instead of left is a perfect tip for this book; I never read that tip before and probably won't ever again in another book. Please keep those coming!

The more the merrier.  I did find some of the tips in the debugging chapter to be basic stuff like James R. pointed out.  On the other hand, by including the basics you wind up with a more complete reference.  It depends on your target audience...if you wish to include newcomers to the VS IDE, by all means include all of the basics.  If your target audience is developers familiar with visual studio fundamentals, then leave out the basic tips.  Consider putting the basic tips' titles and URLs from this site, organized by chapter, in an appendix to the book.