I'm a little behind on my C++ reading.  Today I learning the ins and outs of the C++ AppWizard.  I am using Ivor Horton's “Beginning Visual C++ 6”, but writing the code in VS 2003 ... so make it 7.1 or something like that?  

I have figured out why so many developers that use to do C++ tend to use the Class View in C# more often than others ... they are used to needing one view of their logic.  C++ usually has a .h file and a .cpp file, the class view gives you the combined view ... and then you get to use wizards to generate code in both files at the same time.   This brings me to an observation about how many wizards C++ has .... in fact I am pretty sure there are more wizards in C++ than in VB ;)  ... anyways I don't want to start anything with that last statement but it brings up an idea for a class project that sort of uses Dave Platt's idea of mutltiple homeworks building on large project that will be complete by the end of the term (I think one year it was actually a hex editor!) ... here is my idea:

Could be created in any .net language (C++/CLI, C#, VB, or J#) and would be broken up into some sort of pieces, but in the end you would have a managed version of the functionality that C++'s AppWizard provides for both WinForm and maybe even WebForms.  The final project would need to tie into VS.Net as a Wizard and everything ... lectures I see are:

• Win forms basics
• Win forms advanced
• Win form Controls
• Resource Files and IO (and other related items)
• Database (ADO.Net)
• Code DOM or some way to generate classes
• General good practices on UI layout and flow
• Extending VS.Net
• Setup and deployment
• Good coding standards to follow (for any generated code espcially)