Introduction to C#…
But most independent observations would change this description to “derived from C, C++ and Java.”
Because syntactically C# is very similar to C++ and Java.
As many of the key words are the same for example the same braces ({}) to block a piece of code, (;) for separation of statements from each other and the way to get the data from external source which is out of .NET Environment.
To discuss more about C# language and its associated environment, the .NET Framework, as the most important technology for developers for many years, the following should be considered.
Net Framework as a run time environment for MS Windows 2000 and onward - is a fresh start for Microsoft rather extending the existing code base again and again.
As the point will come that the extension to existing code will become more complex with a passage of time.
The time will come that compatibility will have no value for outdated products.
Finally, caused .Net Frame Work.
.NET is designed to provide a new environment where you can develop almost any application to run on OS (windows).
While C# is a new programming language that has been designed specifically to work with .NET.
Using, C# we can create a classic window desktop application, a database access component, a component of distributed application, a dynamic web page and XML web service.
C# provides a means for you to code up any type of software or component you need to write for the windows platform.
Using, C# we can create a classic window desktop application, a database access component, a component of distributed application, a dynamic web page and XML web service.
C# provides a means for you to code up any type of software or component you need to write for the windows platform.
Need of .NET and C#…
In order to understand the significance of .NET, it is useful to remind that in past history of operating systems, although they may look quite different on the surface, but all of the window operating systems from window 3.1 (introduced in 1992) through windows server 2003 have the same familiar Windows API at their core.
As we progress to the new versions of windows, huge numbers of new functions have been added to the API, but this has been a process of evolving and extending the API rather than replacing it
Microsoft choose this evolutionary approach to software for the obvious reason that it is concerned about the backward compatibility.
Over the years a huge base of third-party software has been written for windows, and windows wouldn’t have enjoyed the success it has had if every time Microsoft introduced a new technology that broke the existing code base!
Backward compatibility is an essential feature of Windows technologies but extending the existing code has a big disadvantage.
Every time technology evolves and add new features it becomes more complicated than it was before.
So now it is clear that in case something had to change. Microsoft could not go on forever extending the same development tools and languages, always making them more and more complex in order to satisfy the conflicting demands of keeping up with the newest hardware and maintaining backward compatibility.
There comes a point where you have to take new start with a clean line if you want a simple yet sophisticated set of languages, environment and developer tools, which make it easy for developer to write state-of-the-art software.
This fresh start is what C# and .NET are all about. Clearly .NET is a framework (An API) for programmers of different skills.
While C# is a language that has been designed from scratch to work with .NET, as will as to take advantage of all the progress and OOP principles that have taken place over the past 20+ years.
We should make it clear that the backward compatibility has not been lost in the process. Existing programs will continue to work, and .NET designed with ability to work with these programs.
Presently communication between software components on windows almost entirely takes place using COM (Component Object Module).
No comments:
Post a Comment