Before .NET The C# programming language was designed for developing programs for Microsoft’s .NET Framework. This chapter will take a brief look at where .NET came from, and its basic architecture. Just to make sure you’re starting on the right foot, let me take this opportunity to remind you of what is hopefully the obvious: C# sharp is pronounced see sharp.
1Windows Programming in the Late 1990s In the late 1990s, Windows programming using the Microsoft platform had fractured into a number of branches. Most programmers were using Visual Basic (VB), C, or C++. Some C and C++ programmers were using the raw Win32 API, but most were using the Microsoft Foundation Classes (MFC). Others had moved to the Component Object Model (COM). All these technologies had their own problems. The raw Win32 API was not object-oriented, and using it required a lot more work than MFC. MFC was object-oriented, but was inconsistent and getting old. COM, although conceptually simple, was complex in its actual coding, and required lots of ugly, inelegant plumbing. Another shortcoming of all these programming technologies was that they were aimed primarily at developing code for the desktop rather than the Internet. At the time, programming for the Web was an afterthought and seemed very different from coding for the desktop.
Comments (3)
Before .NET
The C# programming language was designed for developing programs for Microsoft’s .NET
Framework. This chapter will take a brief look at where .NET came from, and its basic architecture.
Just to make sure you’re starting on the right foot, let me take this opportunity to remind
you of what is hopefully the obvious: C# sharp is pronounced see sharp.
1Windows Programming in the Late 1990s
In the late 1990s, Windows programming using the Microsoft platform had fractured into a
number of branches. Most programmers were using Visual Basic (VB), C, or C++. Some C and
C++ programmers were using the raw Win32 API, but most were using the Microsoft Foundation
Classes (MFC). Others had moved to the Component Object Model (COM).
All these technologies had their own problems. The raw Win32 API was not object-oriented,
and using it required a lot more work than MFC. MFC was object-oriented, but was inconsistent
and getting old. COM, although conceptually simple, was complex in its actual coding, and
required lots of ugly, inelegant plumbing.
Another shortcoming of all these programming technologies was that they were aimed
primarily at developing code for the desktop rather than the Internet. At the time, programming
for the Web was an afterthought and seemed very different from coding for the desktop.
Yes kapil you are right in what you mentioned above...
But i reckon that today windows and web programming are siblings to each other and they are programmed nearly in a similar fashion.
Thank you for posting your comments...
View your on the page
www.sai2viswanath.blogspot.com
thank you
-viswanath