The garbage collector runs periodically within the CLR, automatically restoring the unused memory for inaccessible objects. This model eliminates the low-level details of manipulating the memory of C + + and the involvement of reference counting COM.Bezopasnost types. When you compile an application. NET adds to the assembly information about the classes, their members, etc. This type of data and allows other applications to use them, without requiring additional support files, and compiler – to ascertain the correctness of a query directly into the runtime. This additional level of security is fully eliminates the risk of all types of low-level oshibok.Rasshiryaemye metadata.
Information about the classes and members is only one type of metadata. NET can be stored in a compiled assembly. Metadata describes the code and allow you to provide additional information the runtime and other services. For example, the metadata may indicate the debugger how to run the tracing code, or tell about Visual Studio how design-time should be displayed any special control. They can also be used to enhance more public a service at runtime, for example, to activate transaction or the pool . error handling.
Languages. NET supports structured exception handling that allows you to organize error handling logical and consistent manner, ie, create for different types of errors for the individual blocks and exception handlers placed at a depth of as much as several urovney.Mnogopotochnost. The CLR provides a pool of threads that can be used in different classes. For example, you can asynchronously call methods that read files, or to interact with Web-services without having to explicitly create new threads. Fig. 2 shows a high-level structure of the CLR and the. NET Framework. Fig. 2. CLR and the. NET Framework Fifth fact: ASP.NETyavlyaetsya object-oriented technology It not only provides full access to all objects in. NET Framework, but also allows you to use all the concepts of object-oriented programming (OOP).