Roger.

The problem here is not with .Net per se but with the changes in ISO
standard C++. VS' compiler, per the standard, no longer supports
<iostream.h>. You'll need to use <iostream> (no extension) instead.

Nope.

Many people use

using namespace std;

in source (not in header!!!!)

others will fully qualify names, e.g,

   std::cout

You probably want to check a good text like ones from Herb Sutter for the
gory details, stylistic and otherwise.

Regards,
Will

To expand on Will's statements a bit -

<iostream.h> is the main header file for "classic" or "pre-standard"
IOStreams, as originally produced by AT&T.  <iostream> is the main header
file for "standard" IOStreams, as standardized in the C++ standard (ISO
14882:1998) some six years ago.

VC6 supported <iostream.h> well and <iostream> poorly (VC6 was finalized
before the C++ standard was finished).  VC7 supported both systems, but
began to flag the older pre-standard streams as "deprecated".  VC7.1, aka
VS.NET 2003 dropped support for pre-standard streams altogether.

In many cases, all you need to do is drop the .h and add a using
declaration, or qualify references to the names.  But there are other
differences - for example, pre-standard streams let you specify the sharing
mode when opening a file with an fstream.  Standard iostreams have no
concept of file sharing modes, so if you need that kind of control, you have
to use vendor-specific extensions for support.

There were other (more drastic) changes made to the basic hierarchy of
streams classes, including most significantly, the fact that (nearly) all of
the streams classes are now templates, parameterized on the type of
character you're using (char or wchar_t).

If you're interested in the gorey details, the book "Standard  IOStreams and
Locales" by Angelika Langer and Klaus Kreft is the authoritative work on the
subject.

-cd