Merhaba arkadaşlar.Uzun bir aradan sonra tekrar sizlerleyim tabi bu sefer büyük bir değişiklikle geldim.Paylaşımlarım da elimden geldiğince İngilizce dilini kullanacağım.Bu sizin programcılar dünyasına daha kolay adapte olmanızı sağlıyacaktır.
Şimdi gelelim konumuza.
The .NET Framework is divided into an almost painstaking collection of functional parts, with tens of
thousands of types (the .NET term for classes, structures, interfaces, and other core programming
ingredients). Before you can program any sort of .NET application, you need a basic understanding of
those parts—and an understanding of why things are organized the way they are.
The massive collection of functionality that the .NET Framework provides is organized in a way that
traditional Windows programmers will see as a happy improvement. Each one of the thousands of
classes in the .NET Framework is grouped into a logical, hierarchical container called a namespace.
Different namespaces provide different features. Taken together, the .NET namespaces offer
functionality for nearly every aspect of distributed development from message queuing to security. This
massive toolkit is called the class library.
Interestingly, the way you use the .NET Framework classes in ASP.NET is the same as the way you
use them in any other type of .NET application (including a stand-alone Windows application, a
Windows service, a command-line utility, and so on). Although there are Windows-specific and webspecific
classes for building user interfaces, the vast majority of the .NET Framework (including
everything from database access to multithreaded programming) is usable in any type of application. In
other words, .NET gives the same tools to web developers that it gives to rich client developers.
Hiç yorum yok:
Yorum Gönder