I don't care about the font size. But here are some of my ideas based on the troubles I've had so far and expect to have. First, I think different users need different types of help based on the path they've taken to get to VB.NET. In my case, I migrated from DOS QuickBasic, gradually got into event-driven programming with the VB and Office VBA versions, which naturally led to web programming with ASP, and am now moving to VB.NET/ASP.NET because debugging ASP is a pain. And kicking and screaming all the way, I've incrementally been picking up the thought process behind OOP, classes, inheritance. Here's what I would like to see...
* Intro to Microsoft Data Engine (MSDE) - All the walkthroughs/samples in Help assume you have and know how to use the MSDE. What a pain, trying to figure out how to download, install, create databases, set permissions (on both desktop and server), find and learn to use the OSQL utility, use Access ADP frontend to manage the DB, etc. It's probably simple for those use to dealing with real DBs and writing SQL, but for those of us who's first and only DB was Access, it's a whole new world. There is no concise source for help on this that I could find. MS seems to want us to migrate away from Access, but I need help doing so.
* As others have mentioned, then I'd like to see intro's to dataadapters, data connections, datasets, simple reading and updating, stored procedures, backing up, security, uploading to a server, etc. The VS Help concentrates on binding DBs to controls, but I think their samples are impossible to understand until you first just learn how to read and write to a DB without binding.
* What to use and why? DAO, ADO, ODBC, ADO.NET, etc. Then for text file reading/writing there seems to be at least three ways - FSO, .NET classes, ...etc?
* In VB, I set references from the menu. Now I add references to the Solution Explorer and I add things like "Imports System.Data.SqlClient" to my declaration sections. I get things to work, but I'm not sure I understand what I'm doing yet.
* System Generated Code - When I need to worry about it and when I can ignore it? Discuss.
* Extremely simple Hello World examples of doing various tasks. For example, setting up a class (DLLs, different types of classes?), setting up properties, methods, etc. Then perhaps a simple example of how inheritance works.
* New ways of doing things - Should I/why should I switch from the way I do it now? For example, new ways of defining and using strings.
* Deploying applications - Do I still need programs like InstallShield? Will I still experience DLL Hell?
* XML - I understand the basics of what XML is. But can I live a full life using VB.NET/ASP.NET without becoming an expert and using it directly?
* Along the lines of the XML question - In general, it would be good to get help prioritizing what you need to learn. Since the new stuff is overwhelming. For example, if you want to write a Web Service, these are the areas you need to tackle. If you want to write apps for PDAs and cellphones, these are the things you need to tackle.
I'm sure I can think of more, but this is long enough for now.