CLR Common Language runtime

1: Multi-language support: Just language is oriented toward the CLR . Can be run on this basis.

2: Assembly Load : The DLL files that are packaged by the program are compiled by the CLR (the common language runtime) and loaded into the executable state. Programs that are loaded by the CLR (the common Language runtime) are monitored states: Each node that the program executes is tracked: Monitor the error. Monitor every variable, etc... This kind of monitoring can lose 10% of the performance . But it's really worth the money. Because only in the monitored state: The CLR (Common language Runtime) can do the following:

3: memory allocation : It would have been up to the programmer to take care of it. And to deal with the size of the memory footprint and so on. Existing can be done automatically by the CLR (Common Language Runtime): These are all dependent on the monitoring mentioned above to be completed.

4: garbage collection mechanism : We've always known this thing. But I've never really dealt with it (destroying a common large object doesn't count.) That's just a small part). Because the CLR (Common language Runtime) has been automatically completed:

5. and ensure the separation between the application and the underlying system . There is also a separation between applications: These things are guaranteed to be the proper operation of the application ...

CLR Common Language runtime