If you consider the entire domain of "programming on a windows machine", the .NET framework doesn't cover it all. Remember that .NET was designed for web services, although it's flexible enough for writting standalone apps.

Future versions of Windows will still have the Win32 API in "C-entry" DLL's (otherwise they wouldn't be backwards compatible).
Yes, MS is working towards a fully managed code version of the Win32 API, but guess what it will be calling under the hood .

Host Guest_Robert_MS
Q: Can you clarify the distiction between the WinForm API and the future porting of Win32 to run as a managed API?

A: The "Windows Forms" API is essentially a set of interfaces that expose the existing Win32 functionality via managed code. In the future, you will see the API for developing applications on Windows will evolve into a fully managed API.
I interpret "in the future" as "not in Longhorn". When you read things like "the .net framework will be integrated into the OS" - that's just a fancy way of saying the CLR and all it's functionality will be part of the OS (as appossed to running in user-space).

As for C and C++ on Windows - it will be around as long as Windows is around. Hell, COBOL is still around (if you catch my drift).

gg