Probably simple and easy but .....

Try some of the following links:

http://isle.net/~dude/compsci.htm
http://www.creativeprogrammers.com/article/rd.php/mfc-windows-programming-tutorial-15-1.html
http://www.functionx.com/visualc/
http://tutorials.boxsource.net/categories/48

>however in step 6 where it has the screen shot which is explaining about the white space is called the view.
> I DO NOT see that, all I see are the classes, I do not see any SDI ?? What am I doing wrong ?? :-S  *Whimpers*

Not sure about your question, which Visual C++ version are you using?
Anyway, appears you expect to view this screenshot at design-time, but this is the screenshot at run-time.

You won't see any similar at design-time, like in visual basic, just for dialogs (different from views)

While you can certainly learn MFC programming by looking at samples on the web, may I suggest that you should consider getting a good book to start with. This may seem slow initially, but will be well worth it in the long run to get a broader perspective.

Also (speaking from my own experience), avoid use of the wizards that are built-in with Visual Studio, they simply make it harder to learn.

One book that I found very handy was "Programming Windows with MFC" by Jeff Prosise. I have the 1st edition, which I regard as superior to the 2nd edition, but if you can borrow either one from a library it should be a good place to start.

My final suggestion is to not start with SDI/MDI projects, but start with dialog based projects initially. Get used to the "feel" of MFC that way.

Also, see these:

 http://devcentral.iftech.com/articles/MFC/default.php
 http://baskaronline.tripod.com/MFC1.htm

>>>> create a good looking GUI in visual studio's c++ or c#

C# isn't MS version of C++ but a new Java like programming language that wasn't compiled to machine code like C++ but to an intermediate code that actually was compiled at runtime by a so-called JITter (just-in-time compiler) of .NET that needs to be installed at the target machine before running any DotNet application. Visual Basic .Net and 'Managed C++' can produce a compatible intermediate code, so principally DotNet components can be arbitrarily created and exchanged by VB.net, C# or managed C++.

Visual C++ 6.0 is from 1997/1998 and doesn't know anything of DotNet (2002).

>>>> I DO NOT see that, all I see are the classes, I do not see any SDI

SDI is 'Single Document Interface' and the document and view classes actually are the main part of that interface. You need to build the application and run it by the debugger (F5) to 'see' anything. However, it isn't more than a white screen, some menus and toolbar buttons that could be seen at this step.

Regards, Alex

theres always the win32 api route. i have some examples and tutorials on my site
www.PlanetCpp.com

once you get used to it you can write windows out really fast. i have a wrapper class i wrote so when i need a new window i simply create a new class and add what i need.

In my experience, having a specific goal makes learning how to program easier as well.

Just trying to create a Windows GUI for the sole purpose of learning how to do hasn't seemed to
work well for any of the people I have ever trained.. if you have some concrete goal and direction
the programming will become easier.

The suggestion about using a Dialog based application to begin with is also a great one.  Dialog based apps in MFC
are much simplier and it's easier to get a feel for working with controls.

There are some decent code examples on how to do specific tasks in vc++ available on the web, but you really should look at getting a couple of books ( and again.. knowing what you want to accomplish in the beginning will make picking the right books a lot easier )

You mention both c++ and C#

Depending on what you need to accomplish, if you are starting from the beginning, I would recommend starting with .NET.
The GUI design and control implementation is easier to use ( more result for less work )