C# Programming - .NET Framework - Discussion

1, 2, 3, 4 all these points are the services of CLR.

That's why option c is right.

CLR converts source code to an intermediate code which is further executed by JIT compiler.

How could be the option 2 will be right ?

@venkadesh: me too having same doubt?

It provides a code which is machine independent thats why 1st opt is right, it provides thight security thats why 2nd opt is right, CLR runs nly managed code so 3rd opt is right, and it has automatic garbage collection so 4rth opt is right.

I think option 2 is some what not reletive as how come it will restrict the memory occupancy of other object. (Might be type safety thing would be there).

The runtime automatically handles object layout and manages references to objects, releasing them when they are no longer being used. Objects whose lifetimes are managed in this way are called managed data. Garbage collection eliminates memory leaks as well as some other common programming errors. If your code is managed, you can use managed data, unmanaged data, or both managed and unmanaged data in your .NET Framework application. Because language compilers supply their own types, such as primitive types, you might not always know (or need to know) whether your data is being managed.

These are the basic features of CLS in .Net framework. So the given answer is absolutely right.

This option is absolutly right bcoz CLR is the only one who is responsible to run the managed code and denied to run the unmanaged/Non-cls complient code.

CLR convert source to an intermidiate code that is further executed by JIT compiler.