A lot of people have trouble understanding what .NET really is and what its goals are. Mostly because Microsoft has done a good job of confusing everybody using terms that are not self-explanatory or with terms that mean more that one thing. This editorial will present my thoughts on .NET, what it really is, what its motivations and goals are, and why it is the next "big thing." Should we embrace it or fear it? Both, I daresay.
Permalink for comment
To read all comments associated with this story, please click here.
In the Windows world, is the .NET Framework supposed to completely replace the Win32 API, or is it just a wrapper around it? From what I understand, it is just a wrapper for the Win32 API, which itself is a wrapper around several hundred SDK functions written in C (?)
Also, when using XML to describe how applications are supposed to talk to each other (through the web?), how does this relate to the .NET Framework and the CLR?
I'm starting to understand this slowly, but it's hard to put the pieces together
Here's a couple of questions ...

In the Windows world, is the .NET Framework supposed to completely replace the Win32 API, or is it just a wrapper around it? From what I understand, it is just a wrapper for the Win32 API, which itself is a wrapper around several hundred SDK functions written in C (?)
Also, when using XML to describe how applications are supposed to talk to each other (through the web?), how does this relate to the .NET Framework and the CLR?
I'm starting to understand this slowly, but it's hard to put the pieces together