Answer Posted / kirti

All .NET compilers produce metadata about the types defined in the modules they produce. This metadata is packaged along with the module (modules in turn are packaged together in assemblies), and can be accessed by a mechanism called reflection. The System.Reflection namespace contains classes that can be used to interrogate the types for a module/assembly.

Using reflection to access .NET metadata is very similar to using ITypeLib/ITypeInfo to access type library data in COM, and it is used for similar purposes - e.g. determining data type sizes for marshaling data across context/process/machine boundaries.

Reflection can also be used to dynamically invoke methods (see System.Type.InvokeMember ) , or even create types dynamically at run-time (see System.Reflection.Emit.TypeBuilder).

Why should we go for entity framework?

1012

---

How we can handle the exception at controller level in ASP.Net MVC?

1107

---

What is entity framework? : Entity framework

1057

---

Explain the 'page lifecycle' of an ASP.NET MVC?

1144

---

What are Action Methods in ASP.NET MVC?

1133

---

What are the versions of .net framework?

997

---

explain how you can load related entities in ef (entity framework)?

996

---

Explain bundle.config in mvc4?

1172

---

Can any particular component of .net framework 3.0 be removed?

998

---

Mention what is the difference between “ActionResult” and “ViewResult” ?

1050

---

Which .net framework is installed?

978

---

what is eager loading?

1020

---

What is meant by tempdata in mvc?

1005

---

Why to use '{resource}.axd/{*pathInfo}' in routing in ASP.Net MVC?

2727

---

What is difference between html.beginform and ajax.beginform?

1009

---